After a search of bugs I have followed the advice of Sandro in Bug#153750 and I'm trying to re-open the bug ---------------> ------- Comment #9 From Sandro 2006-11-13 11:06 PST [reply] ------- //snip// Please reopen if it doesn't work for you. -----------------> //beecrypt-4.1.2-r1 emerge ERROR output, followed by "emerge --info" and then full output for failed beecrypt-4.1.2-r1 emerge. ------------> !!! ERROR: dev-libs/beecrypt-4.1.2-r1 failed. Call stack: ebuild.sh, line 1576: Called dyn_compile ebuild.sh, line 945: Called src_compile beecrypt-4.1.2-r1.ebuild, line 63: Called die !!! emake failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.10" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" and of course, the output of emerge --info -----------------> one rob # emerge --info Portage 2.1.2_rc3-r4 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r1 i686) ================================================================= System uname: 2.6.19-gentoo-r1 i686 AMD Athlon(tm) 64 Processor 3700+ Gentoo Base System version 1.12.7 Last Sync: Wed, 13 Dec 2006 05:30:01 +0000 dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 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.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer" 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" LANG="en_AU.UTF-8" LINGUAS="en" 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/portage /usr/local/portage/xgl-coffee" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow 3dnowext X a52 aac aalib alsa alsa_cards_emu10k1 arts asf avi bash-completion berkdb bitmap-fonts bonobo browserplugin bzlib cairo cdparanoia cdr cli cracklib crypt cups dbus dlloader dri dv dvd dvdr dvdread eds elibc_glibc emboss encode esd fam ffmpeg firefox fortran freetype gdbm gif gimp glitz gnome gpm gstreamer gtk gtk2 hal iconv imlib imlib2 input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog java javascript jpeg kde kernel_linux ldap libg++ linguas_en mad mikmod mjpeg mmx mmxext mp3 mpeg mpg mplayer ncurses nls nptl nptlonly nsplugin nvidia offensive ogg opengl oss pam pcre pdf pdflib perl png ppds pppd print python qt3 qt4 quicktime readline real reflection sane scanner sdl session spell spl sse sse2 sse3 ssl svg svga tcpd tga tiff totem truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l vcd video_cards_fbdev video_cards_nv video_cards_nvidia video_cards_v4l video_cards_vesa vorbis win32codecs wmf wmv x86 xine xml xorg xsane xv xvid zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS --------------------->
*** Bug 158111 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > *** Bug 158111 has been marked as a duplicate of this bug. *** > This has happened three times now, I submit a bug and it duplicates itself .. why? I only click on the commit button once. Is it the browser, or my ISP?
Created attachment 104009 [details] emerge output for beecrypt-4.1.2-r1 Full failed emerge output for beecrypt-4.1.2-r1
Ok, tried emerge with CFLAGS="-march=i686 -O2 -pipe" and it emerged. I don't know what this will do to my general setup though, or if it will effect something else in turn. Will let you know if it busts anything else. I tried this because of the following warning in the ebuild; --> ewarn "The MMX assembler code presents TEXTREL issues. If you don't want them try using" ewarn "relaxed CFLAGS like -march=i686 instead of -march=pentium3 and so on." ewarn "This ebuild fails on multilib system with multilib-strict on AMD64." ewarn "Feel free to help upstream solving the above bugs." ------> What does that all mean?
(In reply to comment #4) > Ok, tried emerge with CFLAGS="-march=i686 -O2 -pipe" and it emerged. Looking at your emerge log: i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DOPTIMIZE_X86_64 -march=athlon64 -O2 -pipe -fomit-frame-pointer -DNDEBUG -fomit-frame-pointer -Wa,--noexecstack -c base64.c -fPIC -DPIC -o .libs/base64.o it seems that using -march=athlon64 with x86 arch exploit a bug in configure script. Using athlon64 let configure assume you're building for amd64 arch. > I tried this because of the following warning in the ebuild; > --> > ewarn "The MMX assembler code presents TEXTREL issues. If you don't want them > try using" > ewarn "relaxed CFLAGS like -march=i686 instead of -march=pentium3 and so on." > ewarn "This ebuild fails on multilib system with multilib-strict on AMD64." > ewarn "Feel free to help upstream solving the above bugs." > ------> > What does that all mean? that the ebuild could fail if you use FEATURES="stricter" as first issue. If you want to learn more about textrel see "HOWTO Locate and Fix .text Relocations (TEXTRELs)" http://www.gentoo.org/proj/en/hardened/pic-fix-guide.xml
CCing amd64 people because this bug affect only -march=athlon64 even if only with x86 arch. I'll try to solve this next week, I'll be away until monday.
Fixed in cvs. Commit message: Fix incorrect behaviour with CHOST="i686-..." and CFLAGS="-march=athlon64 ...", bug #158109. Thanks to Robert Golding <robert.golding@gmail.com> for reporting. Solution adopted: Filtering with-arch=athlon64 when CHOST doesn't begin with x86_64, reverting to CHOST as default.
*** Bug 158724 has been marked as a duplicate of this bug. ***
I(In reply to comment #8) > *** Bug 158724 has been marked as a duplicate of this bug. *** > Fixed in CVS. Fix incorrect behaviour with CHOST!="x86_64-..." and any -march flags related to x86_64, including athlon64 and k8 fixing also bug #158724.
