when i try to emerge sci-libs/blas-atlas-3.6.0-r1, i got this : ----- I am now going to ask for two C compilers, and their associated flags. The first such set (CC & CCFLAGS) are used in compiling the non-generated ATLAS code. This code is written in normal C, and responds well to high levels of optimization. Typically, this is set to your default compiler, and your highest levels of optimization. The second set of C compilers (MCC & MMFLAGS) is used to compile the generated ATLAS code. Generated codes are written at a very low-level (think of C used as a kind of portable assembler). On many platforms, high levels of optimization are detrimental, as the compiler tries to pipeline a perfectly pipelined code, and succeeds in reducing performance substantially (this occurs on DEC ALPHAs & Sun UltraSparcs, for instance). If the default does not work for you, try a midrange optimization such as -O. The generated code does not alias any output arguments, so aliasing optimizations should be OK. Enter ANSI C compiler(CC) [/usr/bin/gcc]: Enter C Flags (CCFLAGS) [-fomit-frame-pointer -O -mfpmath=387 -m64]: ----- and then a prompt which doesn't work. emerge --info : ----- Portage 2.1-r2 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.17-gentoo-r4 i686) ================================================================= System uname: 2.6.17-gentoo-r4 i686 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.12.4 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] 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-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -O2 -pipe -msse2" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=athlon-xp -O2 -pipe -msse2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://85.25.128.62" LANG="fr_FR.utf8" LC_ALL="fr_FR.utf8" LINGUAS="fr fr_FR" 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" PORTDIR_OVERLAY="/usr/portage/local/layman/musicbrainz /usr/portage/local/layman/pro-audio" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 apm avi berkdb bitmap-fonts cli crypt cups dbus dlloader dri eds emboss encode foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal imlib ipv6 isdnlog jack jackmidi jpeg libg++ libwww mad motif mp3 mpeg ncurses nls nptl nptlonly ogg opengl pam pcre pdflib perl png pppd python qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode vorbis xml xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_fr linguas_fr_FR userland_GNU video_cards_radeon video_cards_vesa video_cards_fglrx" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Hi Thomas, Looking at your specs, the problem you're encountering very like is due to the fact that blas-3.6.0 isn't able to detect your CPU properly and bombs out. In this case, you will have to go with the blas-atlas version in ~x86 which has much better support for modern CPUs. To really figure out your problem we'd need to see the actual error message that blas-atlas produces. blas-atlas generates a bunch of log-files ending in *.LOG in the emerge directory. If you look through them you might find a more specific error message that will shed some more light on this. Thanks, Markus
Hi Markus, i've been looking into my /var/tmp/portage ... dirs, and I found a file called ConfDump.log which contains this line : CONFIG/tst.c:1: d
Hi Markus, i've been looking into my /var/tmp/portage ... dirs, and I found a file called ConfDump.log which contains this line : CONFIG/tst.c:1: désolé, pas implanté: mode 64 bits pas compilé en (translation : sorry, not implemented 64 bitsmode not compiled in ) i've got this line 55626 times (!!). By the way, when the emerge failed and i had to kill it from outside, I had to kill a process xconfig which was taking 100% of my cpu time. Anyway, thanks for your advice. I simply added lapack-atlas to my portage.keywords and it didn't bother anymore with downgrading blas-atlas to the buggy version. thanks for your help. Thomas (In reply to comment #1) > Hi Thomas, > > Looking at your specs, the problem you're encountering very like is > due to the fact that blas-3.6.0 isn't able to detect your CPU properly > and bombs out. In this case, you will have to go with the blas-atlas > version in ~x86 which has much better support for modern CPUs. > To really figure out your problem we'd need to see the actual > error message that blas-atlas produces. blas-atlas generates a bunch > of log-files ending in *.LOG in the emerge directory. > If you look through them you might find a more specific error message > that will shed some more light on this. > > Thanks, > Markus >
Hi Thomas, I am glad that the unstable version works for you now. We're in the process of moving the 3.7.11 versions of blas-atlas/lapack-atlas into stable and these should play much nicer with modern CPUs such as yours. Your error (assuming my high school French doesn't trick me ;-) ) indeed indicates that atlas has problems dealing with some 64 bit aspect of your CPU >CONFIG/tst.c:1: d
Hi Thomas, I am glad that the unstable version works for you now. We're in the process of moving the 3.7.11 versions of blas-atlas/lapack-atlas into stable and these should play much nicer with modern CPUs such as yours. Your error (assuming my high school French doesn't trick me ;-) ) indeed indicates that atlas has problems dealing with some 64 bit aspect of your CPU >CONFIG/tst.c:1: désolé, pas implanté: mode 64 bits pas compilé en >(translation : sorry, not implemented 64 bitsmode not compiled in ) Since there's really nothing we can do about this particular version, I'll close this bug as CANTFIX. Thanks, Markus
