This is the mail archive of the 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: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

   I can understand the FSF gcc developers' frustration at
the lack of participation by the darwin developers. However
I still think it merits at least understanding why r131198
is breaking the linkage on darwin. It may well be that darwin
to exposing a latent bug in the use of install-leaf.

On Fri, Feb 29, 2008 at 11:04:24AM -0800, Mark Mitchell wrote:
> Jack Howarth wrote:
>> Richard,
>>     This problem appears to be caused by...
>> Author: rsandifo
>> Date: Thu Dec 27 11:26:06 2007
>> New Revision: 131198
>> URL:
>> Log:
>> libgcc/
>>         * (all): Use install-leaf rather than install.
>>         (install): Split most of the rule into...
>>         (install-leaf): ...this new one.
> It's certainly desirable to fix this before the release, but Darwin bugs 
> are not release blockers for 4.3.0.
> The GCC SC has been discussing the Darwin situation.  There are two basic 
> criteria for being a primary platform: (1) utility to users of the FSF GCC 
> releases, and (2) active maintenance.  There hasn't been enough in the way 
> of active maintenance for Darwin to make it possible to maintain Primary 
> Platform status for Darwin for 4.3.0.
> That statement doesn't imply anything about what status Darwin might have 
> in the future; if there's active maintenance -- as, it looks like, there 
> may very well be, given that we have a volunteer for the position -- then 
> that might well reactivate Darwin, even for later 4.3.x releases.
> Thanks,
> -- 
> Mark Mitchell
> CodeSourcery
> (650) 331-3385 x713

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