Build log follows... Portage 2.1.2_rc3-r9 (default-linux/alpha/2006.1/desktop, gcc-4.1.1, glibc-2.3.6 -r5, 2.6.18.2 alpha) ================================================================= System uname: 2.6.18.2 alpha EV56 Gentoo Base System version 1.12.7 Last Sync: Fri, 22 Dec 2006 23:50:01 +0000 dev-java/java-config: 1.2.11 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="alpha ~alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-mieee -pipe -O3 -mcpu=ev56" CHOST="alpha-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /et c/texmf/web2c" CXXFLAGS="-mieee -pipe -O3 -mcpu=ev56" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/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=/di stfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://michigan/gentoo-portage" USE="alpha X alsa alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_ asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pc m_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugin s_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug al sa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_p lugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plu gins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol bash-completion berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dlloader dri dvd dvdr elibc_glibc encode esd fam fortran gdbm gif gpm gstreamer gtk iconv input_devices_evdev inp ut_devices_keyboard input_devices_mouse ipv6 isdnlog jpeg kde kernel_linux libg+ + mad mikmod mp3 mpeg ncurses nis nls nptl nptlonly ogg opengl oss pam pcre pdf perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl session spel l spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode userland_GNU vid eo_cards_glint vorbis xml xorg xv zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGU AS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 104672 [details] Output of "ebuild ... compile"
(In reply to comment #1) > Created an attachment (id=104672) [edit] > Output of "ebuild ... compile" > Hi Stefaan, Thanks for pointing this out. I'll see that I can get rid of the -m32 in atlas' build system for alpha. Hopefully that'll do. Best, Markus
I've disabled the explicit 32/64 bit arch selector in the ebuild for alpha. However, atlas' build system will still do some auto-detection but will hopefully refrain from passing -m32 on alpha. Unfortunately, I can't test this myself. Hence, could you please test and let me know if it works for you! Thanks, Markus
Created attachment 105275 [details] "emerge blas-atlas" for patched version Tried "emerge blas-atlas" after cvs up, unfortunately, there seems to be more to it :( It now fails on "-m64", and it seems to do so the first time in work/ATLAS/gentoo-build (during unpack), and persists on doing so during the compilation process.
Hi Stefaan, Thanks for the quick response! Somehow I knew that this would be happening since upstream has significantly overhauled their build system and "officially" only supports x86, x86-64 and sparc, AFAIK. I'll have a look at it and hopefully we can get rid of that pesky -mXX flag. Best, Markus
Any news on this one? i got the same error but -m64 on 3.7.32
(In reply to comment #6) I assume you mean the same error as I had in comment #4 then? Unfortunately, no further news :(
I think this one will have to wait for upstream, since the build system clearly has trouble detecting alpha properly. Even if I'd be able to get rid of the -m64 somehow there's still no guarantee that the build does anything sensible and may very well result in a pretty crummy library. We just discussed this among the sci devs and have tentatively decided to make the blas|lapack|cblas-reference ebuilds the default for the blas|lapack|cblas-virtual instead of the *-atlas ebuilds as presently. The reference ebuilds should be a much easier and faster compile and provide more than adequate libraries. Currently only the alpha keyword is missing for blas-reference lapack-reference cblas-reference Hence, if you guys could have a look and possibly keyword these that would be great. Otherwise, I'll file a separate bug about this when I have some more time on the weekend. Thanks, Markus
Okay, i've keyworded those ebuilds ~alpha.
Well, i've removed -m64 from blas-atlas and lapack-atlas, and everything seems fine.
(In reply to comment #10) > Well, i've removed -m64 from blas-atlas and lapack-atlas, and everything seems > fine. > Thanks, let's close this one then.
