Michael Haubenwallner
Fri, 25 May 2007 13:27:47 -0700
On Fri, 2007-05-25 at 21:02 +0200, Fabian Groffen wrote: > On 25-05-2007 14:01:06 -0500, Jason Pepas wrote: > > Fabian Groffen wrote: > >> What's your path? Where does the compiler come from? > > > > well, I am assuming that prefix-launcher is meddling with my PATH, so I > > don't think I can easily tell you. > > > >> Out of curiosity, did you ever try bootstrapping using > >> bootstrap-prefix.sh? If so, did that get past point 1.3 of > >> http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml? > > > > yeah, I started out using bootstrap-prefix.sh about a week ago. the first > > time I used it it worked, and then I started over from scratch a few days > > later and something was broken, so I decided to try out prefix-launcher. > > Ok, that is vague, but indicates some problem with where prefix-launcher > gets the compiler from.
When emerging coreutils with eprefix-bootstrap in stage 'basics', binutils-2.16.1 and gcc-4.1.2 are already from the new eprefix. Maybe we should try to not be sticked to binutils-2.16.1 during bootstrap ? But wait, prefix-launcher can build binutils-2.17 without texinfo, although the patch[1] is not applied... [1] http://thread.gmane.org/gmane.linux.gentoo.alt/2386 Btw, I'm bootstrapping an eprefix on sparc-solaris2.9 now too (being one of the slowest machines here...) /haubi/ -- [EMAIL PROTECTED] mailing list