************************* emerge error ************************* ATLAS install complete. Examine ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details. make[1]: Leaving directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' make -f Make.top shared-strip arch=Linux_21264GOTO_2 make[1]: Entering directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' mkdir -p gentoo/libs Linking a really big library, please be patient... cd gentoo/libatlas.a ; \ libtool --mode=link --tag=CC /usr/bin/gcc -o libatlas.la *.lo -rpath /usr/lib ; \ libtool --mode=install install -s libatlas.la /var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS/gentoo/libs libtool: link: `ATLU_cusergemm.lo' is not a valid libtool object libtool: install: `libatlas.la' is not a valid libtool archive Try `libtool --help --mode=install' for more information. make[1]: *** [libatlas.so] Error 1 make[1]: Leaving directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' make: *** [shared-strip] Error 2 !!! ERROR: sci-libs/blas-atlas-3.6.0-r1 failed. !!! Function src_compile, Line 114, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. ************************* emerge --info ************************* Portage 2.0.54 (default-linux/alpha/2005.0, gcc-3.3.2, glibc-2.3.5-r3, 2.6.14.2 alpha) ================================================================= System uname: 2.6.14.2 alpha EV68AL Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5, 2.4.2 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 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.15.92.0.2-r10 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r4 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-pipe -O3 -mcpu=ev67" CHOST="alpha-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /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/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-pipe -O3 -mcpu=ev67" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="alpha X alsa arts audiofile berkdb bitmap-fonts bzip2 cli crypt cups curl dri eds encode esd exif expat f77 fam font-server foomaticdb fortran gd gdbm ggi gif glut gnome gpm gstreamer gtk gtk2 idn imagemagick imap imlib ipv6 jpeg kde lcms ldap libg++ libwww mad mikmod mng motif mp3 mpeg nas ncurses nls ogg oggvorbis opengl oss pam pcre pdflib perl plotutils png python qt quicktime readline reflection samba sdl server session spell spl ssl tcpd tetex tiff truetype truetype-fonts type1-fonts udev vorbis xml2 xmms xorg xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
If you run it interactively with 'interactive=1 emerge blas-atlas', what is the default CPU choice? This looks suspiciously like the PPC issue we've been having.
Could you give more detailed instruction please? How can I find out the default CPU choice? BTW, in CXXFLAGS it is set `-mcp=ev67' and cat /var/tmp/portage/blas-atlas-3.6.0-r1/temp/environment |grep cpu shows: CFLAGS='-pipe -O3 -mcpu=ev67' CXXFLAGS='-pipe -O3 -mcpu=ev67' grep -qs 'UML' /proc/cpuinfo; MY_CCFLAGS="-O3 -mcpu=v8"; MY_MMFLAGS="-O -mcpu=v8"; MY_CCFLAGS="-O3 -mcpu=ultrasparc"; MY_MMFLAGS="-O -mcpu=ultrasparc"; Thank you very much :-) (In reply to comment #1) > If you run it interactively with 'interactive=1 emerge blas-atlas', what is the > default CPU choice? This looks suspiciously like the PPC issue we've been > having. >
(In reply to comment #1) I'm having the same problem: Portage 2.1-r2 (default-linux/alpha/2006.1, gcc-3.4.6, glibc-2.3.6-r4, 2.6.16.19 alpha) ================================================================= System uname: 2.6.16.19 alpha EV6 Gentoo Base System version 1.12.1 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-r4 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-mieee -pipe -O3 -mcpu=ev6" CHOST="alpha-unknown-linux-gnu" CONFIG_PROTECT="/etc /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/terminfo" CXXFLAGS="-mieee -pipe -O3 -mcpu=ev6" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig 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" PORTDIR_OVERLAY="/usr/local/sci" SYNC="rsync://fileserver/gentoo-portage" USE="alpha berkdb bitmap-fonts bzip2 cli crypt cups dlloader doc dri examples fortran gdbm hdf hdf5 ipv6 isdnlog kerberos ldap libg++ ncurses nls nptl nptlonly pam pcre perl ppds pppd python qt readline reflection session spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode xml xorg zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU video_cards_cirrus video_cards_ati video_cards_dummy video_cards_fbdev video_cards_glint video_cards_mga video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_v4l video_cards_vga video_cards_voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS ATLAS install complete. Examine ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details. make[1]: Leaving directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' make -f Make.top shared-strip arch=Linux_21264GOTO make[1]: Entering directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' mkdir -p gentoo/libs Linking a really big library, please be patient... cd gentoo/libatlas.a ; \ libtool --mode=link --tag=CC /usr/bin/gcc -o libatlas.la *.lo -rpath /usr/lib ; \ libtool --mode=install install -s libatlas.la /var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS/gentoo/libs libtool: link: `ATLU_cusergemm.lo' is not a valid libtool object libtool: install: `libatlas.la' is not a valid libtool archive Try `libtool --help --mode=install' for more information. make[1]: *** [libatlas.so] Error 1 make[1]: Leaving directory `/var/tmp/portage/blas-atlas-3.6.0-r1/work/ATLAS' make: *** [shared-strip] Error 2 !!! ERROR: sci-libs/blas-atlas-3.6.0-r1 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile blas-atlas-3.6.0-r1.ebuild, line 115: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. alpha-10 ~ # cat /var/tmp/portage/blas-atlas-3.6.0-r1/temp/environment |grep cpu CFLAGS='-mieee -pipe -O3 -mcpu=ev6' CXXFLAGS='-mieee -pipe -O3 -mcpu=ev6' MY_CCFLAGS="-O3 -mcpu=v8"; MY_MMFLAGS="-O -mcpu=v8"; MY_CCFLAGS="-O3 -mcpu=ultrasparc"; MY_MMFLAGS="-O -mcpu=ultrasparc";
Unfortunately, I can not test on alpha, but this error indicates that there was a problem compiling one of the PIC objects and the build hence fails during linking. Could you please try 3.7.11 which is currently being stabled on most arches and see if that works! Thanks, Markus
Alpha, maybe you could check that again and confirm the current version is working.
(In reply to comment #5) > Alpha, maybe you could check that again and confirm the current version is > working. > Can't test it, blas-atlas-3.6.0-r1 fails to check the USE-flags of gcc-4.1.2, and newer blas-atlas doesn't work: bug 159002
3.8.0 is stable, so this is fixed
