darwin may lose primary target status on FSF gcc

[Toby Peterson]

On Fri, Sep 18, 2009 at 17:26, Jack Howarth <howarth at bromo.med.uc.edu> wrote:
> On Sat, Sep 19, 2009 at 12:19:38AM +0000, Eric Hall wrote:
>> On Fri, Sep 18, 2009 at 07:57:53PM -0400, Jack Howarth wrote:
>> > On Fri, Sep 18, 2009 at 11:46:57PM +0000, Eric Hall wrote:
>> > > On Fri, Sep 18, 2009 at 07:38:15PM -0400, Jack Howarth wrote:
>> > > >   There is hope! We have an analysis of the exact
>> > > > breakage in eh under 10.6 for gcc trunk...
>> > > >
>> > > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025908.html
>> > > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025909.html
>> > > >
>> > > > The breakage in gcc trunk is due to the additional epilog unwind
>> > > > information which darwin's unwinder (which is always used under
>> > > > 10.6 since symbols in libgcc-10.5 always come from libSystem)
>> > > > doesn't understand. The possible fixes are either to 1) not add
>> > > > the additional epilog unwind information on darwin or 2) have
>> > > > the gcc driver on darwin implicitly pass -no_compact_unwind to
>> > > > the link line. Cheers.
>> > > >            Jack
>> > >
>> > >
>> > >   Did someone care somewhere in here?
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > macports-dev mailing list
>> > > macports-dev at lists.macosforge.org
>> > > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>> >
>> > If anyone here cares whether gcc 4.5.0 exists in a usable form
>> > on darwin10, I should hope so. These were courtesy emails for
>> > the gcc44 maintainers here to let the know that someone is
>> > working the issue. If darwin support for gcc isn't tended to
>> > you'll eventually stuck running g95 (oh..wait...g95 doesn't
>> > build on darwin10...never mind).
>>
>>
>>       Huh, funny, this 'Xcode' thingy installs a compiler,
>> seems like it works too.  I'm thinking that sort of thing
>> is going to continue in the future.
>>       Is there a reason there's ongoing discussion of
>> gcc 4.x on a macports related list instead of on a gcc
>> list?
>>
>>
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
> Gee, I must be missing something from my SL Xcode
> installation....where is the fortran *thingy*?
>              Jack
> ps No one is forcing you to read the posts.

Given current reality, you're probably better off contributing to
llvm-gfortran... or better yet, a native fortran front-end for llvm.
FSF gcc is barely relevant on our platform these days.

- Toby