Summary: | building with gcc2 from stage1 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pascal de Bruijn <pmjdebruijn> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | azarah |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pascal de Bruijn
2005-07-23 06:44:43 UTC
What stage did you use, as an old gcc2 stage1 should not have glibc_2.3 issues ... I used this one: ftp://ftp.nluug.nl/pub/os/Linux/distr/gentoo/releases/x86/2005.0/stages/x86/stage1-x86-2005.0.tar.bz2 Anyway the oldest stages I can find are from 2004.0, and those are probably with gcc 3.2.3. Is the glibc 2.3.5 dependancy really needed for libsandbox? Isn't it possible to do a stage1 without libsandbox? Yeah, you cannot use those stage .. they with gcc-3.3.x. If you really want to try, add '-sandbox' to FEATURES, and rebuild sandbox against glibc-2.2.5. @azarah: CANTFIX? Hmm probably... When I tried using -sandbox, the build process went fine, until I stumbled upon an error, which after some googling had something to do with glibc 2.3.x being backward incompatible with glibc 2.2.x. So this was a no go! Then I found a historical stage1 tarball, but on this tarball, I couldn't get portage properly running, because it was too much out of date. (Yes, I tried emerge portage itself first, but that wouldn't work either). So I finally gave up... So, CANTFIX would probably be very appropriate! Anyway thanks for the suggestions. Somebody with a gcc2 box that is fairly up to date, and catalyst knowledge needs to build some stages I guess :/ |