Summary: | Missing g++ program when bootstraping, reopening 77718 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Garth <garth> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2004.3 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | gcc's config.log file after gcc failed compiling when following #77718 workaround |
Description
Garth
2005-02-01 22:39:00 UTC
Created attachment 50244 [details]
gcc's config.log file after gcc failed compiling when following #77718 workaround
The work-around of bug #77718 didn't work directly. the step: emerge --nodeps gcc failed with: checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/gcc-3.4.3-r1/work/build/gcc/xgcc -B/var/tmp/portage/gcc-3.4.3-r1/work/build/gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 checking for C compiler default output... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. make[1]: *** [configure-target-libstdc++-v3] Error1 make[1]: Leaving directory `/var/tmp/portage/gcc3.4.3-r1/work/build' make: *** [profiledbootstrap] Error 2 !!! ERROR: sys-devel/gcc-3.4.3-r1 failed. !!! Function gcc_do_make, Line 1079, Exitcode 2 !!! make failed with profiledbootstrap config.log is atached I did find a way to work around it, but it seems highly inneficient. 01. explode 2004.3-stage1 02. bind proc 03. chroot into it 04. env-update 05. source /etc/profile 06. emerge sync 07. tweek my make.conf 08. emerge --nodeps linux26-headers 09. USE="-multilib" emerge --nodeps gcc 10. cd /usr/portage 11. scripts/bootstrap.sh (this step will fail at some point) 12. FEATURES="-sandbox" emerge --nodeps gcc 13. rm /var/run/bootstrap-progress 14. scripts/bootstrap.sh (Note, step 14 is currently being done at time of writing, but it seems to progress properly.) I can now comfirm that the work-around I gave work (bootstrap completed) |