Mailing List Archive

GCC 3.4 and MacOSX
Hello,

I'm a gentoo user on my AMD box and I'm using also gentoo for MacOSX on my
iBook because there're some libraries I need to work on a project.
Unfortunately, seems like the gcc's bug #15834
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15834) blocks the build of a
lot of software, like libmatroska and my project which links to wefts and
libebml (which is also the problem for libmatroska).

There's a way to install gcc 3.4 on MacOSX (maybe tweaking it to resolve
that bug), so that I can build libmatroska and my project?

Thanks in advance,
--
Diego "Flameeyes" Pettenò
dgp85@users.sourceforge.net - http://flameeyes.web.ctonet.it/



--
gentoo-osx@gentoo.org mailing list
Re: GCC 3.4 and MacOSX [ In reply to ]
On Oct 3, 2004, at 6:11 AM, Diego 'Flameeyes' Pettenò wrote:

> There's a way to install gcc 3.4 on MacOSX (maybe tweaking it to
> resolve
> that bug), so that I can build libmatroska and my project?

Probably just installing gcc-3.4 from source tarball via "make
bootstrap" would work... but here is an email from the
darwin-developers list:

> From: shebs@apple.com
> Subject: Re: gcc3.4 plus Apple's gcc3.3
> Date: September 30, 2004 4:11:29 PM MDT
> To: jmzorko@mac.com
> Cc: darwin-dev@lists.apple.com
> jmzorko@mac.com wrote:
>
>>
>> Hello, all ...
>>
>> I am involved in porting a C++ class framework we use at work to OSX
>> / Darwin PPC so we can target OSX as well as Win32 and Linux. This
>> code demands gcc3.4, which shouldn't be an issue (gcc3.4 "make
>> bootstrap" seemed to work just fine on my 1.33GHz 12" PowerBook), but
>> I would like to, if possible, use gcc-select to choose between
>> Apple's gcc3.3 and FSFs gcc3.4. Has anyone else done this? I've not
>> researched how I would approach doing this yet (this posting is part
>> of that research <smile>).
>
> It's just a shell script that you could hack up, but I don't recommend
> you try - FSF 3.4 is missing dozens of features essential to building
> Mac apps, such as framework path searching, alignment pragmas, and
> similar kinds of bits. Some of those features are needed by system
> headers and could cause interesting (heh) runtime problems. Ultra
> portable pure ISO/K&R C code, such as what GCC itself is written in
> (for reasons that should be obvious), will be OK, but just one Cocoa
> or Carbon call can mess you up.
>
> So I recommend you install gcc-3.4 under its own name only, and
> have all of your 3.4-using code ask for 3.4 explicitly by name.
>
> Stan


--
gentoo-osx@gentoo.org mailing list