See comments in the forum: http://forums.gentoo.org/viewtopic-t-472432-highlight-emerge+python.html SO as a summary: I followed strictly the guidelines in the simple installation guide and upgrading the compiler. Then after successfully compiling several packages, the python emerge fails. Also doing a simple emerge python. See in --info python is still 2.4.2 ... epi Python-2.4.3 # emerge --info Portage 2.1.1_pre1-r2 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.3.6-r4, 2.6.16-gentoo-r9 i686) ================================================================= System uname: 2.6.16-gentoo-r9 i686 VIA Nehemiah Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r2 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomit-frame-pointer -ffast-math -finline-functions" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomit-frame-pointer -ffast-math -finline-functions" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X X509 a52 aac aalib acpi alsa apache2 apm asf audiofile auth avi bash-completion berkdb bigger-fonts bigpatch bitmap-fonts bittorrent bl bluetooth bootsplash bzip2 canna ccache cdda cddb cdf cdio cdparanoia cdr cdrom chasen chroot cjk cle266 cli cpudetection crypt cscope css ctype cups dba directfb discard-path dlloader dpms dri dts dv dvd dvdr dvdread ecaggressive ecmark2 elibc_glibc encode ethereal exif expat fam fastbuild fastcgi fat fbcon fbdev fbsplash ffmpeg flac flood foomaticdb force-cgi-redirect gd gdbm gif gmp gphoto2 gstreamer gtk gtk2 gtkhtml icecast idn ieee1394 imlib isdnlog jpeg jpeg2k kernel_linux lame lcd lcms libwww lirc lm_sensors mad matroska memlimit mikmod mime minimal mmx mng mod_python mp3 mp4live mpeg mpeg2 mplayer mythtv nas nls nptl ogg oggvorbis openal openssh openssl pam patented pcre pda pdf pdflib png posix pppd python qt quicktime rc5 rdesktop readline real reflection reiser4 reiserfs scp sdl session sftp shout simplexml skey sndfile soap sockets speex spell spl sse sse-filters ssl stream subtitles subversion tcltk tcpd theora tiff tokenizer transcode truetype udev unichrome unicode userland_GNU utf8 v4l v4l2 vcd vlm vorbis win32codecs wma wma123 wxwindows x11vnc x264 x86 xine xml xml2 xmms xorg xsl xv xvid xvmc zlib input_devices_mouse input_devices_keyboard video_cards_via video_cards_vesa" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Please choose the 'Gentoo Linux' product next time you file a bug.
Also see bug 138268.
gotta go to wranglers
this bug report contains no info post all relevant information into your bugreport ... external links to forums doesnt cut it as those just waste our time trying to figure out what you're talking about
Created attachment 90361 [details] emerge --info
Created attachment 90363 [details] emerge dev-lang/python-2.4.3-r1 This is an unmasked python-2.4.3 emerge. It shows exactly the same error as the original "emerge -e system". I used this version so when starting python I can see when it displays python 2.4.2 (the one installed by the portage-20060623.tar.bz2) and 2.4.3 that I try to emerge
Started installing my system according to "Gentoo Linux x86 Quick Install Guide". Used: stage3-i686-2006.0.tar.bz2, portage-20060623.tar.bz2. After having my system running on its own, emerged gcc-4.1.1, according to the document "Gentoo Linux GCC Upgrade Guide". Following the procedure I started an "emerge -e system". That went well until after about 47 packages, python got emerged. This failed. I attached the output from - emerge --info and - emerge python this shows the same problem that occurred during "emerge -e system"
What cpu is that? Can you attach /proc/cpuinfo and check if the problem persists if you start over with CFLAGS="-O2 -march=c3 -pipe" (not just remerge python with those, start over)? Also, if /proc/cpuinfo does not list "cmov" under "features", use an i586 or "lower" stage tarball.
Created attachment 90372 [details] cat /proc/cpuinfo The processor is also described on these pages (SP8000): http://da.gentoo-wiki.com/HARDWARE_Epia_SP8000 I succeed compiling and running the kernel once with the gcc-4.1.1. as an i686 model. cpuinfo seems to report cmov instruction support. On the Internet there are contradicting reports (old SP8000 motherboards seemed to be equiped with CPU's without cmov). Until now I always suppose mine had because everything seemed to work OK.
As you know, while installing, unpacked, unfinished work is left in /var/tmp/portage/... I played with this. Following instruction from the log indicated where compilation started to go wrong: case $MAKEFLAGS in \ *-s*) LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3:/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 CC='i686-pc-l inux-gnu-gcc -pthread' LDSHARED='i686-pc-linux-gnu-gcc -pthread -shared' OPT='-DNDEBUG -march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomi t-frame-pointer -ffast-math -finline-functions' ./python -E ./setup.py -q build;; \ *) LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3:/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 CC='i686-pc-linu x-gnu-gcc -pthread' LDSHARED='i686-pc-linux-gnu-gcc -pthread -shared' OPT='-DNDEBUG -march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomit-f rame-pointer -ffast-math -finline-functions' ./python -E ./setup.py build;; \ esac Doing this interative on the command line, in this directory a ./python -> tells me this is a python 2.4.2 build with gcc-3.4.4 (so seems to link with old python lib LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 ; ./python -> still reports a python 2.4.2 with gcc-3.4.4 (still linking with old python) export LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 ; ./python -> still reports a python 2.4.3 with gcc-4.1.1. That is what I would expect. I don't know how I can test this version ... is there a way to run testcases that don't depend on the modules that are not build yet. Another conclusion yesterday doing the following instruction LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3:/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 CC='i686-pc-linu x-gnu-gcc -pthread' LDSHARED='i686-pc-linux-gnu-gcc -pthread -shared' OPT='-DNDEBUG -march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomit-f rame-pointer -ffast-math -finline-functions' python -E ./setup.py build;; \ Note python -E ... not ./python. So I used to already installed 2.4.2 to build the modules of the 2.4.3 finished succesfully! But again, I don't know exactly how to test the result. So my conclusions is that there's some mixup of libraries with the preinstalled version and the one that I'm emerging. I could be big time wrong of course ...
(In reply to comment #10) (edited for readability) > Doing this interative on the command line, in this directory a > ./python -> tells me this is a python 2.4.2 build with gcc-3.4.4 (so seems to > link with old python lib > > LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 ; ./python > -> still reports a python 2.4.2 with gcc-3.4.4 (still linking with old python) But that is not what the build is doing. The build is doing "LD_LIBRARY_PATH=stuff ./python" (no ";" like you have), which is equivalent to your "export" below, which works. > LD_LIBRARY_PATH=/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3:/var/tmp/portage/python-2.4.3-r1/work/Python-2.4.3 > CC='i686-pc-linu > x-gnu-gcc -pthread' LDSHARED='i686-pc-linux-gnu-gcc -pthread -shared' > OPT='-DNDEBUG -march=c3 -Os -msse -mmmx -mfpmath=sse -pipe -fomit-f > rame-pointer -ffast-math -finline-functions' python -E ./setup.py build;; \ > > Note python -E ... not ./python. So I used to already installed 2.4.2 to build > the modules of the 2.4.3 finished succesfully! But again, I don't know exactly > how to test the result. But with that LD_LIBRARY_PATH you should be using the 2.4.2 python binary with 2.4.3's libpython now, which is pretty weird. Does indicate there's something wrong with the compiled python binary though. > So my conclusions is that there's some mixup of libraries with the preinstalled > version and the one that I'm emerging. I could be big time wrong of course ... Unless I've misread the build output I do not believe that is the problem. Your cpuinfo confirms this is one of the c3 cpus that should work with an i686 CHOST and compiler flags (the ones with a samuel core do show up as "i686" in uname but do not work with an i686 CHOST because of a missing cmov instruction afaik). Your CFLAGS (and cpu) are sufficiently unusual that I would really like to see if this is reproducable with just -O2 -march=c3 -pipe (or possibly -march=c3-2, but try -march=c3 first).
(In reply to comment #11) > Your cpuinfo confirms this is one of the c3 cpus that should work with an i686 > CHOST and compiler flags (the ones with a samuel core do show up as "i686" in > uname but do not work with an i686 CHOST because of a missing cmov instruction > afaik). Your CFLAGS (and cpu) are sufficiently unusual that I would really like > to see if this is reproducable with just -O2 -march=c3 -pipe (or possibly > -march=c3-2, but try -march=c3 first). I followed your advise and emerge python (version 2.4.2 or 2.4.3) succeeded! Later I started experimenting to find what option(s) cause the failure. It was the -ffastmath. Thank you so much for pointing me right to the problem ... I consider this defect as resolved. PS However, one cannot imagine, afterwards I wanted to resume my installation by doing again the "emerge -e system" and the next morning I found out that my HD did crash ... :-(((
Don't think it's necessary to filter a flag like -ffast-math which really doesn't belong in system CFLAGS because it changes the behaviour of code (see man gcc).
