I committed a new revision of the gcc-apple compiler yesterday.  This
compiler is fixed NOT to use libraries from /usr, but from EPREFIX
instead.  I noticed this, because when I threw away normal portage on my
Darwin 7 box yesterday I broke my compiler (it was using libs from
/usr, installed by normal portage there).  Of course on that machine
this was a major pita, as compilation of gcc takes half a day there.
But that problem aside.

The other change in this ebuild is the use of gcc-config, and the
installation in such a way that we can install multiple compilers next
to each other (maybe I'll pull in a 3.3 compiler from Apple just for
fun).  This might come in handy when FSF GCC4 starts to compile and run
on OSX, such that we can easily try out, and switch back when necessary.

The problem now is that for some (still unknown) reason (to me) the
gcc-config profile the ebuild is to generate isn't generated/installed.
I don't see any errors, but I don't see the profile either.  This causes
gcc-config to fail to switch to it, and effectively leave your system
without a compiler.  The profile can be manually made, but instead I'd
just like all OSX users to wait with this latest ebuild, till I got it
sorted out why it doesn't work.

On a sidenote: how long does it take for x86-macos users to build the
gcc-apple compiler?


-- 
Fabian Groffen
Gentoo on a different level
-- 
[EMAIL PROTECTED] mailing list

Reply via email to