Re: ANN: GCC 4.9.0 (2014) for Max OS X Mavericks

[Simon Wright <simon@pushface.org>]

marioeroy@gmail.com writes:

> On Sunday, June 1, 2014 5:06:04 AM UTC-4, Simon Wright wrote:
>>
>> ...
>> 
>> GNAT GPL 2014 (for Mac) supports C, C++, Ada, and Objective C. My
>> release additionally supports Fortran and Objective C++. In all
>> cases, the compiler itself is built without change. I had to rebuild
>> the command 'gnat', because the original build with the compiler
>> failed with SIGSEGV; something to do with exceptions, I need to
>> report this but I'm a bit too vague on the details.
>> 

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61027

> I could not get the work around using gprbuild to work on Mavericks
> 10.9.5. The gnat -v (specifying an invalid argument) still
> crashes. After many attempts have finally tracked this down.

Do you mean that the 'gnat' I provided doesn't work, or that you've
tried to rebuild gnatcmd as I did and *that* didn't work?

I'm still using gcc-4.9.0-x86_64-apple-darwin13-2014-1.tar.bz2 without
problems (except that other gnat* commands still show the problem when
used in ways which result in program exit via exception, such as
'gnatchop -h', or gnatmake when the library contains .ali files from a
very old compiler release).

I just rebuilt gnatcmd (Xcode 6.0.1 on Mac OS X 10.9.5, Darwin 13.4.0)
and ./gnatcmd -v works fine.

> One needs to pass --with-host-libstdcxx=-lstdc++ when configuring
> GCC. Gnat will no longer SIGSEGV after make install.

Thanks for the info. That must have been _some_ detective work!

I see from my compiler build log that my gnat* commands were built with
(a mammoth list of inputs, including)

   -B../../../x86_64-apple-darwin13/libstdc++-v3/src/.libs 
   -B../../../x86_64-apple-darwin13/libstdc++-v3/libsupc++/.libs 
   -L../../../x86_64-apple-darwin13/libstdc++-v3/src/.libs 
   -L../../../x86_64-apple-darwin13/libstdc++-v3/libsupc++/.libs 
   -static-libstdc++

which presumably means to use the newly-build libstc++ in GCC rather
than the system one? Interesting, because the rebuilt gnatcmd doesn't
appear to use libstdc++ at all (I eventually managed to get a build that
used libgnat.dylib, of course that itself might have bound libstdc++
statically - but then how would my fix work?)