| 1 |
On 25-05-2007 22:27:38 +0200, Michael Haubenwallner wrote: |
| 2 |
> > Ok, that is vague, but indicates some problem with where prefix-launcher |
| 3 |
> > gets the compiler from. |
| 4 |
> |
| 5 |
> When emerging coreutils with eprefix-bootstrap in stage 'basics', |
| 6 |
> binutils-2.16.1 and gcc-4.1.2 are already from the new eprefix. |
| 7 |
|
| 8 |
Ohw... ok. |
| 9 |
|
| 10 |
> Maybe we should try to not be sticked to binutils-2.16.1 during |
| 11 |
> bootstrap ? |
| 12 |
> But wait, prefix-launcher can build binutils-2.17 without texinfo, |
| 13 |
> although the patch[1] is not applied... |
| 14 |
> [1] http://thread.gmane.org/gmane.linux.gentoo.alt/2386 |
| 15 |
|
| 16 |
Problem of that patch is that it is not what we want in the main tree |
| 17 |
for a normal installation of the package. |
| 18 |
|
| 19 |
> Btw, I'm bootstrapping an eprefix on sparc-solaris2.9 now too (being one |
| 20 |
> of the slowest machines here...) |
| 21 |
|
| 22 |
I can imagine... |
| 23 |
|
| 24 |
I want /var/tmp mountable install stages, so we don't need this hell of |
| 25 |
getting this crap straight. But I guess for prefix launcher there is no |
| 26 |
other option then applying the patch and emerging binutils-2.17.* |
| 27 |
|
| 28 |
-- |
| 29 |
Fabian Groffen |
| 30 |
Gentoo on a different level |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-alt@g.o mailing list |
Archives