silly thing just loops and loops until you kill -9 it: Enter ANSI C compiler(CC) [/usr/lib/ccache/bin/gcc]: Enter C Flags (CCFLAGS) [-fomit-frame-pointer -O -mfpmath=387 -m64]: Compiling with = '/usr/lib/ccache/bin/gcc -fomit-frame-pointer -O -mfpmath=387 -m64' doesn't seem to work for me. Enter 1 to try different CC/flags, 0 to continue anyway [1]: 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/lib/ccache/bin/gcc]: Enter C Flags (CCFLAGS) [-fomit-frame-pointer -O -mfpmath=387 -m64]: Compiling with = '/usr/lib/ccache/bin/gcc -fomit-frame-pointer -O -mfpmath=387 -m64' doesn't seem to work for me. Enter 1 to try different CC/flags, 0 to continue anyway [1]: 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/lib/ccache/bin/gcc]: Enter C Flags (CCFLAGS) [-fomit-frame-pointer -O -mfpmath=387 -m64]: make: *** [config] Terminated /usr/portage/sci-libs/blas-atlas/blas-atlas-3.7.11.ebuild: src_compile aborted; exiting. sandbox: Caught signal 2 in pid 26528 Portage 2.1.2_pre2-r7 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.16.16 x86_64) ================================================================= System uname: 2.6.16.16 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.14 Last Sync: Tue, 10 Oct 2006 17:50:02 +0000 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.4.3-r4 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.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://85.25.128.62 ftp://212.219.56.134/sites/www.ibiblio.org/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo" 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/local/portage" SYNC="rsync://rsync12.de.gentoo.org/gentoo-portage" USE="x86 X berkdb bitmap-fonts cli crypt cups dlloader dri elibc_glibc fortran gdbm gpm input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog kernel_linux libg++ ncurses nls nptl nptlonly pam pcre perl ppds pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts udev unicode userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i740 video_cards_i810 video_cards_imstt video_cards_mga video_cards_neomagic video_cards_nsc video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
I see the same thing when I try to emerge blas-atlas-3.7.17 as recommended in bug 136003. I was wondering why after more than one hour it was still compiling but then I did $ grep smmcase0 sci-libs\:blas-atlas-3.7.17\:20061027-173247.log make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 139 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 139 make[6]: *** [smmcase0] Error 1 make[6]: *** [smmcase0] Error 1 Hmm, around that message I see smm.c:80:5: #error "This kernel requires x86-64 assembly!" make[6]: *** [smmcase0] Error 1 make[5]: *** [mmucase] Error 2 At other places in the log I see smm.c:88:5: #error KB must be multiple of 16! smm.c: In function `ATL_sJIK120x120x104TN104x104x0_a1_b1': smm.c:209: error: `vector' undeclared (first use in this function) smm.c:209: error: (Each undeclared identifier is reported only once smm.c:209: error: for each function it appears in.) smm.c:209: error: syntax error before "float" smm.c:212: error: syntax error before "float" smm.c:219: error: syntax error before "unsigned" smm.c:240: error: syntax error before "float" and lots of other error message, but not the same #error message as above. I don't know exactly where it cycles but I guess I could send the full log if that would help solving the problem. (I just need to build it because scipy obviously depends on it, if there would be a way to get scipy without blas-atlas I would be happy, too.)
Hi Peter, Thanks for you report! This doesn't solve the blas-atlas problem, but scipy depends on virtual/blas/lapack and you should therefore be able to use the blas/lapack-reference ebuilds instead of the blas/lapack-atlas ebuilds. Thanks, Markus
Markus, thanks for the hint emerge blas-reference lapack-reference scipy works beautifully. (Now I have to see how to actually use it...)
Folks, is this still an issue with the latest version in portage (3.7.30)? Thanks, Markus
Folks, I am closing this since bug since we now have blas-atlas-3.8.0 stable and this shouldn't be an issue any more. Thanks, Markus
