For the last month I have been trying to update glibc-2.3.1-r2 to 2.3.2 but it fails every time. The error vary depending on when it is emerge: 1. /usr/portage/distfiles/ & /var/tmp/portage/ empt, error as atttachement test.txt 2. second try with glibc tbz2 already downloaded, error as attachement text0.txt Reproducible: Always Steps to Reproduce: 1. rm -rf /usr/portage/distfiles/*, rm -rf /var/tmp/portage/* 2. emerge -u glibc or emerge glibc 3. Actual Results: see attachement test.txt and test0.txt Expected Results: compile without error Portage 2.0.47-r10 (default-ppc-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.20-ppc-r3 ppc GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="dvd nls mitshm ppc gnome-libs alsa arts guile postgres esd ldap pcmcia pnp trusted gphoto2 X opengl xv fbcon kde qt gnome gtk gtk2 bonobo evo gb gtkhtml motif tcltk aalib imlib ncurses readline sdl lcms gif jpeg png tiff gd avi mpeg quicktime oss xmms oggvorbis encode snmp ggz pam ssl crypt imap tcpd mozilla spell truetype xml xml2 pdflib plotutils java perl python ruby slang libwww libg++ berkdb mysql odbc innodb gdbm samba gpm apache apache2 usb cups" COMPILER="gcc3" CHOST="powerpc-unknown-linux-gnu" CFLAGS="-O3 -pipe -mcpu=750", (have also tried with -02 same results) CXXFLAGS="-O2 -pipe" ACCEPT_KEYWORDS="ppc ~ppc" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="ccache" have a /var partition of 5G
tom seems that the attachments aren't present, could you try sending them again?
Created attachment 10502 [details] result from emerge glibc this is the result of emerge glibc with /usr/portage/distfiles & /var/tmp/portage empty
Created attachment 10503 [details] test0.txt
Created attachment 10504 [details] make.conf file
Created attachment 10505 [details] new emerge of glibc with error code ...! probably more useful...
Created attachment 10506 [details] details of just added emerge... (emerge glibc > emerge_glibc_0_details.txt a 8 m file for emerge_glibc_0_details.txt is available if necessary... just let me know. thx for the help...
Created attachment 10510 [details] 2nd emerge today after rm -rf and emerge rsync result of emerge glibc after emerge rsync rm -rf /usr/portage/distfiles/* rm -rf /var/tmp/portage/* emerge glibc error but at different place then before emerge...
Created attachment 10511 [details] details of emerge glibc 1 details of 2nd emerge...
Please emerge again portage, then emerge glibc
Created attachment 10560 [details] after doing emerge portage, emerge rsync, emerge glibc... As recommended I proceeded to do the following: emerge portage emerge rsync emerge glibc half way through my system crashed... have to restart my pc so that fsck will recover crashed system... after restarting I get the following: 1. All partition are recover, but only user partition has the following message: error message: "clearing orphaned inode ...." 2. when starting X get the following error message: "/etc/X11/startDM.sh: line 1: /etc/conf.d/basic no such a file or directory"
Created attachment 10566 [details] for good measure I tried another emerge glibc... for good measure I tried an emerge glibc again This time without emerge portage or emerge rsync the following occured also check emerge_glibc_3_details, next attachement
Created attachment 10567 [details] the emerge output details.... look in preceding update... detail of emerge_glibc_3.txt
Double check your ram and hd cosistency seems more a HW failure than a software issue =/
Yes, with the randomness of issues here combined with our inability to reproduce, this definitely sounds like a hardware problem. Even if not, if we can't reproduce it we can't fix it, so unless something develops in the next day or two, we'll have to WORKSFORME it.
marked as worksforme, since there is no reply from tom.
Sorry about not getting back earlier... Still cannot emerge glibc, now it even crashes my system... I have change my kernel to benh-r10, check memory and hardware all is ok on hardware side, but still same pb... One thing I noticed recently, although not always reproductible, is that when it crashes, it is very often when my screen goes into screensaver mode... I have disabled xscreensaver... but not sure which other app i should disable to completely disable powerdown of screen... if you could let me know, I then could check that last possibility as a possible cause of crashes... thx for the help
Please test booting from the livecd and chroot build the glibc
wild guess: could you set ACCEPT_KEYWORDS="~ppc" instead of ACCEPT_KEYWORDS="ppc ~ppc" one thing I've noticed in your output logs is that offtime.c __offtime function fails Can you try again by emerging gcc and latest ppc-sources kernel first? Feel free to use this kernel config: http://dev.gentoo.org/~pvdabeel/kernel/
Hello, I have done as Pieter suggested... run into trouble emerging gcc... similar type of error was observed on X86 so I added my info to that bug: Bug # 24906 have resolved erratic segfaulting though, it was L2 cache related. Using: sysctl -w kernel.l2cr=0 Since I have done that only recently and tried to compile (unsuccessfuly) gcc, i have not tried to compile glibc... I thaught it would be better to have gcc compiled first...the upgrade glibc... Would gcc-3.3 be safe if successfuly compiled or would it crashes my apps...? Thank you again for all the help... I really hope I can solve this puzzle... and finally get newest gcc and glibc to work on my machine..
This definately has to be related to bad memory or some other hardware problem. I'm totally unable to reproduce it.
