From my post on the gentoo forums bugs forum: I'm having problems installing gentoo 1.3b or 1.4 beta... from stage1... I'm using a Duron at 850 mHz... Everytime i try to emerge system... it fails at compiling perl... Here's the error output.. (from 1.4 beta) CCCMD = cc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -march=athlon-tbird -O3 -pipe -fomit-frame-pointer /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/../../../../i686-pc-linux-gnu/bin/as: relocation error: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/../../../../i686-pc-linux-gnu/bin/as: symbol strncasecmp, version GLIBC_2.0 not defined in file libc.so.6 with link time reference make: *** [perly.o] Error 1 !!! Error: The ebuild did not complete successfully !!! Function src_compile, Line 42, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/sys-devel/perl/perl-5.6.1-r5.ebuild . I also tried this on an Athlon-XP... and it got by the perl stage... same compiler flags... except athlon-xp instead of athlon-tbird...
Please assign to a c/c++ programmer, this is kinda out of my league. Thanks!
Euhm, one more thing, since when is a duron a thunderbird? :o) Try using CFLAGS that fit your CPU ;o) That might help. Thanks
I thought that the Duron Spitfires ( the earliest Duron CPU's could take the athlon-tbird compile flags... since i think all they differed in was the L1 and L2 cache sizes)... but i'll try it with just the plain athlon compile flag ( but i thought this flag was supposed to be for the first slot A athlons) Pat.
Lostlogic - this looks like a gcc compiling issue. Any thoughts? I can help with resetting any perl compile flags you can think of, but don't have a 1.3/1.4 box (or gcc 3.x installed/knowledge) to even think about playing with this on.
Well what i did was downclock my Duron to 600 mHz... which is what it should be... and changing the compiler flags to -march=athlon -O3 -pipe.. Well... what happened during the bootstrap... was that i got an internal compiler error... during the 2nd build of gcc-3.2_pre... i'm talking about Gentoo 1.4 beta... So what i did... was tried it again... same settings... the bootstrap was successful... and then... during emerge system... this is what i got when emerging perl.. toke.c:6400:43: macro "__string2_lbptr_p" requires 9 arguments, but only 1 given toke.c: In function `S_scan_heredoc': toke.c:6400: `__string2_lbptr_p' undeclared (first use in this function) toke.c:6561:34: macro "__string2_lbptr_p" requires 9 arguments, but only 1 given toke.c: In function `S_scan_inputsymbol': toke.c:6561: `__string2_lbptr_p' undeclared (first use in this function) make: *** [toke.o] Error 1 !!! Error: The ebuild did not complete successfully. !!! Function src_compile, Line 42, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/sys-devel/perl/perl-5.6.1-r5.ebuild. So i dunno what's up with this... but what i'm going to do is try CFLAGS="-march=i686 -O3 -pipe" I'm assuming that doing this will be successful... but i'd kinda like the compiling to use CFLAGS="-march=athlon -O3 -pipe" or CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer" It seems that using the -march=athlon-tbird didn't really matter on the early Durons (without sse). My overclocking's not a problem either... it was running stable at 850 mhz... and having problems when downclocking to 600 mhz confirms this... I have another system with an athlon-xp 1700+... i bootstrapped and emerged system just fine... but i did have some trouble emerging kde-libs... and kde-base... i got compile errors for those two emerges... but when i re-ran the compiles... it was able to emerge them successfully the 2nd time... strange... the compiler flags i used for the athlon-xp was CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer".. Well if there anything else you'd like me to try... just tell me... and i'll try to do it... i don't really know much about compiling... so i can't really help u with suggestions about setting perl compile flags... i'm not even sure what that means... but it does sound like a gcc-3.2_pre bug... and it's also strange that it's failing on perl.. Pat.
Well... i tried re-doing the bootstrap... this time with compiler flags -march=i686 -O3 -pipe -fomit-frame-pointer.. The first attempt... the bootstrap was successfull... but then during emerge system... there was a seg fault during the perl compile.. The 2nd attempt... it didn't even make it through the bootstrap... it failed during the gcc compile.. This could be a gcc-3.2 problem... so maybe i'll wait until a new gcc-3.2 version comes out... then try again... but it's strange that perl fails on me also... whether the arch is athlon... athlon-tbird... or i686... it doesn't matter..
hi... i just wanted to let u know... that after gcc-3.2 final was released... i tried again to compile gentoo 1.4 beta... the bootstrap was fine... but this is what i got when i compiled perl during emerge system: toke.c In function `Perl_yylex': toke.c:5165: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropiate. See <URL:http://www.gnu.org/software/gcc/bugs/html> for instructions. make: ***[toke.o] Error 1 !!! Error: The ebuild did not complete successfully. !!! Function src_compile, Line 42, Exitcode 2. !!! (no Error message) !!! emerge aborting on /usr/portage/sys-devel/perl/perl-5.6.1-r6.ebuild. Then what i did... was unmask perl-5.8.0-r2... and i got the exact same error message.. I'm compiling on a Duron 850... with CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer"
I suspect that the -march should be athlon, not athlon-tbird (this from a rather cheap surface scan of google). I know you were going to try a few things tonight, thought I'd pass that tidbit on. Searched for "gcc duron march" and came back with a lot of people with the exact same problem. Not your technical answer, but hopefully a start.
Okay... sorry this took so long... to rule out a hardware problem... i tried the bootstrap on another Duron system... and it work... both perl versions... included the one u fixed... emerged... the flags i used were -march=athlon -O3 -pipe... I think it's a hardware problem... because i tried those same flags on the original duron system... and the perl emerge failed.. So at this point i think it's a hardware problem... i'll try to bootstrap on the original Duron system... to make sure..
Okay... so what happened was.. On the motherboard in the system that was causing compile errors... there were 3 sticks of memory in all 3 slots... but i somehow lost awareness of the fact that the 3rd of those memory slots is bad... some of the contacts burned out a while back... and i forgot about that... so i took that stick of memory out... and now i have no problems with perl... or the odd strange error.. I'm sorry about that.. Pat.
wow.
