| 1 |
Hi, |
| 2 |
|
| 3 |
I found the problem why bootstrap.sh fails: |
| 4 |
I used gentoo/releases/x86/2004.3/stages/x86/stage1-x86-2004.3.tar.bz2 for a |
| 5 |
stage1 install. During bootstrap sys-devel/gcc-config seems not to get |
| 6 |
updated. So an old version is used which does not handle the new GCC path in |
| 7 |
/usr/lib/ correctly; that is, gcc 3.4.2 and up will install to /usr/lib/gcc |
| 8 |
instead of /usr/lib/gcc-lib. This leads to strange errors (cannot find gcc) |
| 9 |
and entries in /etc/env.d/gcc/config. |
| 10 |
To bypass this problem you only have to copy a newer version of gcc-config |
| 11 |
to /usr/bin/ after doing an "emerge sync" but before running |
| 12 |
"scripts/bootstrap".sh: "cp |
| 13 |
/usr/portage/sys-devel/gcc-config/files/gcc-config-1.3.6 |
| 14 |
/usr/bin/gcc-config" |
| 15 |
|
| 16 |
Furthermore installing GCC 3.4, Kernel 2.6 and NPTL seems to work with |
| 17 |
default-linux/x86/2005.0, too. You only have to adjust the files which |
| 18 |
reside in /etc/portage (introduced with portage version 2.0.50); that is, |
| 19 |
allowing ~x86 to be applied for gcc, glibc, libstdc++-v3 (in |
| 20 |
package.keywords) and setting virtual/kernel, virtual/os-headers to |
| 21 |
linux26-headers (in profile/virtuals). |
| 22 |
|
| 23 |
Regards |
| 24 |
Philipp Hasse |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives