This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libffi problem

From: Bo Thorsen <bo at sonofthor dot dk>
To: Jeff Sturm <jsturm at one-point dot com>, "H. J. Lu" <hjl at lucon dot org>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 17 Jul 2002 17:21:26 +0200
Subject: Re: libffi problem
References: <Pine.LNX.4.44.0207171100370.19377-100000@ops2.one-point.com>

On Wednesday 17 July 2002 17:15, Jeff Sturm wrote:
> On Wed, 17 Jul 2002, H. J. Lu wrote:
> > Are you maintaining libffi?
>
> I'm not.  I only have write-after-approval.  Anthony Green maintains the
> sourceware libffi, I don't know if he's responsible for the same in gcc,
> or whether they are actively kept in sync.

They're nowhere near in sync. The sourceware one is far behind the gcc one.

> I assume it's an oversight that libffi isn't mentioned in MAINTAINERS?

Yes it is. At least for as long as gcc/libffi and sourceware/libffi is 
different, we either need a specific maintainer for it...

> If nobody else, I'd think the CPU maintainers would be qualified to
> review/approve libffi ports.

... or do this. I don't care which is chosen, as long as something is done.

Bo.

-- 

     Bo Thorsen                 |   Praestevejen 4
     Free software developer    |   5290 Marslev
     SuSE Labs                  |   Denmark

References:
- Re: libffi problem
  - From: Jeff Sturm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]