Summary: | glibc-2.4 doesn't compile with gcc-3.4 on ppc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Frank Hollenbach <frank.hollenbach> |
Component: | [OLD] Core system | Assignee: | PPC Porters <ppc> |
Status: | RESOLVED WONTFIX | ||
Severity: | critical | CC: | bjt23, hiyuh.root, morgoth6, toolchain |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Frank Hollenbach
2006-03-11 00:59:14 UTC
dropped ~ppc KEYWORDS as i only tested with gcc-4.1.0 i'll leave it up to the ppc team to see if they want to go the route of adding 'ppc? ( >=sys-devel/gcc-4 )' to the DEPEND ... (In reply to comment #1) > dropped ~ppc KEYWORDS as i only tested with gcc-4.1.0 > > i'll leave it up to the ppc team to see if they want to go the route of adding > 'ppc? ( >=sys-devel/gcc-4 )' to the DEPEND ... > Yeah, I've build glibc-2.4 with gcc-4.1.0 just now like SpanKY said. since the dep is >=gcc-4.1 we have to wait to have it unmasked. expected time within the next week, I hope The problem is not only related to gcc 3.x. I give a try to glibc 2.4 last weekend and it seems it require -mlong-double-128 or -mabi=ibmlongdouble. My current system uses gcc 4.0.2 and this option is not valid for this version too, but it works perfectly with gcc 4.1. Anyway I doesn't recomended to compile glibc using gcc 4.1 when system default compiler is diffrent because it cause some ugly problems (For example __guard symbol breackage, but this can be easy solved be recompiling broken package) I will try 4.0.3 maybe this version supports -mlong-double-128 IBM extended format. ive updated the glibc-2.4 ebuild to require gcc-4.0 or better *** Bug 131171 has been marked as a duplicate of this bug. *** Can someone please contribute a formal solution to this ? I have tried adding "-mabi=ibmlongdouble" xor "-mlong-double-128" to my /etc/make.conf CFLAGS, but neither addition causes the configure to work properly. I have [ebuild R ] sys-devel/gcc-4.1.1 USE="altivec fortran gtk nls -bootstrap -build -doc -gcj -hardened -ip32r10k -mudflap -multislot -nocxx -objc -objc++ -objc-gc -vanilla" 0 kB [ebuild U ] sys-libs/glibc-2.4-r3 [2.3.6-r3] USE="nls nptl nptlonly -build -glibc-omitfp -hardened -profile" 0 kB I don't understand why this is WONTFIX ... Are PPC users not privileged to upgrade to glibc-2.4 ? I mean, if glibc-2.4 doesn't work, mask it, but please don't refuse to fix breakage ... The formal solution is to emerge gcc-4.1.1 (our stable compiler) and then switch to it with gcc-config (or eselect). glibc-2.4 *must* be compiled with gcc-4, we won't be supporting compiling it with gcc-3.4, sorry. It looks like you haven't switched compilers yet, just because it's installed doesn't mean that it's the current compiler. Good luck! Actually, I was messing around with this, and it seemed that the problem was that crossdev was incorrectly trying to compile glibc with the *host* gcc, rather than the cross compiler. I ended up running crossdev in stages, for glibc doing: CC=powerpc-unknown-linux-gnu-gcc sudo crossdev -s3 powerpc I did do this with gcc 4.1.1, not sure if this will work with 3.x. Note that just using 4.1.1 as the default system compiler and running crossdev as you'd expect it should work (just doing a stage 4 x-compile from the beginning) did NOT work, and failed with the same "this configuration requires..." error when trying to build glibc. you probably did something wrong then, `crossdev powerpc` works fine for me |