I was able to get bbconf-1.10 to compile and run in a ~amd64 system, though it took some tweaking to CFLAGS in make.conf: if "-fPIC" is not set, the build fails. I suspect that I should also note that doing a 'CFLAGS="-fPIC" emerge bbconf' will also fail (if -fPIC is not in CFLAGS in the make.conf file), possibly because while CFLAGS will have '-fPIC" appended to it, CXXFLAGS(="${CFLAGS}", in my make.conf) will not (and bbconf uses C++ and Qt). I'm not sure if there's a fix for this (or even if there should be one), but I'm just reporting what I see... Reproducible: Always Steps to Reproduce: 1. If necessary, modify /etc/make.conf to set the "-fPIC" flag in CFLAGS (and CXXFLAGS, if its contents are not dependent on CFLAGS). 2. Create overlay version of bbconf-1.10.ebuild that has "~amd64" added to KEYWORDS 3. emerge bbconf Actual Results: bbconf was built successfully, and ran just fine. Expected Results: nothing different - this is more of a confirmation that it works than a prolem Not sure if you'd need info on my mildly-tweaked (I guess) system, but as per instructions, here's the results of an "emerge info": Portage 2.0.53 (default-linux/amd64/2005.1, gcc-4.0.2, glibc-2.3.6-r1, 2.6.14-gentoo-r2 x86_64) ================================================================= System uname: 2.6.14-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 2800+ Gentoo Base System version 1.12.0_pre11 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.16 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-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe -fPIC" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe -fPIC" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa avi berkdb bitmap-fonts bzip2 crypt cups dvd dvdr dvdread eds emboss encode expat flac foomaticdb fortran gif gmp gnome gpm gstreamer gtk gtk2 imlib jack jpeg kde lcms lzw lzw-tiff mng mozilla mp3 mpeg ncurses nptl nptlonly nsplugin ogg opengl pam pcre pdflib perl png python qt quicktime readline sdl sndfile spell ssl tcpd theora threads tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS I'll leave my severity rating at "Normal", since anyone running blackbox on a 64-bit system will probably want bbconf...
Created attachment 74194 [details, diff] -fPIC patch Here is the -fPIC patch now it needs some multilib-strict love. You should never add -fPIC to your CFLAGS it will broke your system.
(In reply to comment #1) > Created an attachment (id=74194) [edit] > -fPIC patch > > Here is the -fPIC patch now it needs some multilib-strict love. > You should never add -fPIC to your CFLAGS it will broke your system. Probably true, though on my semi-minimal (for now) system, the only thing that this gave me problems with was glibc. I may go rebuild everything (again!), assuming that your patch works OK for me...
please provide a patch to fix the problem with FEATURES=multilib-strict if you're still interested in getting this keyworded
