I think that link to /usr/bin/gcc - it as mistake, because you will broke illumos-gate build.
We have to save illumos-gate build based on current userland. We can use different compilers and have changes in build system. For example: I have used Richard's gcc4 for building some components in userland without modifications on current system. -Igor From: Colin Ellis <[email protected]> Reply-To: OpenIndiana Developer mailing list <[email protected]> Date: Sat, 12 Nov 2011 16:46:10 +0000 To: OpenIndiana Developer mailing list <[email protected]> Subject: Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2 > Additional changeset to fix up copyright headers > > https://bitbucket.org/cellis_oidev/oi-build/changeset/29819e8e803f > > On Sat, Nov 12, 2011 at 3:23 AM, Josef 'Jeff' Sipek <[email protected]> > wrote: >> On Mon, Nov 07, 2011 at 04:48:05PM +0000, Colin Ellis wrote: >>> > https://bitbucket.org/cellis_oidev/oi-build/changeset/170076b03654 >>> > >>> > use Makefile.bootstrap files for gcc3 :) >> >> Ooooh! So, to build it the first time, I need to 'gmake -f >> Makefile.bootstrap' for the libs, then gcc. Once I have them installed, I >> can ignore the bootstrap files? >> >> Why are there two packages - one for gcc and one for the runtime? It seems >> to me that using facets would be the better way. >> >> Since we have a new enough pkg in /experimental, we can use mediated links >> to manage /usr/bin/gcc (as well as g++, etc.). I think it'd be worth having >> them. >> >> Jeff. >> >> -- >> Failure is not an option, >> It comes bundled with your Microsoft product. >> >> _______________________________________________ >> oi-dev mailing list >> [email protected] >> http://openindiana.org/mailman/listinfo/oi-dev > > _______________________________________________ oi-dev mailing list > [email protected] http://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
