Somehow the --libdir to ./configure is always specified with leading double slashes like //usr/lib... this is inconsistent with the rest of the paths. Example from windowmaker ./configure: ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=//usr/lib --sysconfdir=/etc/X11 Of course it is a legal path unfortunately there is software that depends on the "shorter" version. One example is ruby software using mkmf.rb, as mkmf.rb is comparing strings to resolve if two paths are the same. I'm not sure if this should be fixed in the core eclasses (probably toolchain.eclass) or if it should be fixed on the ebuild level. If it is decided to not fix this here I will submit a bug for the ruby ebuild instead. Merry Christmas :-) Reproducible: Always Steps to Reproduce: Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 x86_64) ================================================================= System uname: 2.6.9-gentoo-r1 x86_64 4 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /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/gconf /etc/terminfo /etc/env.d" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://ftp.du.se/pub/os/gentoo http://mirror.pudas.net/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 acpi alsa apache2 arts berkdb bitmap-fonts cdr crypt dvd dvdread emacs esd f77 fam flac fortran gd gdbm gif gphoto2 gpm gtk imagemagick imlib ipv6 java jp2 jpeg junit ldap libwww lzw lzw-tiff mikmod motif multilib mysql ncurses nls oggvorbis opengl oss pam pdflib png postgres python qt readline ruby sdl slang snmp ssl tcpd tetex tiff truetype usb userlocales xml2 xmms xpm xrandr xv zlib"
I've also noticed that there are several occurances of "/usr/lib" in windowmaker ebuild, which should probably be replaced by "/usr/$(get_libdir)".
econf does this
fix is prob something like this: --- ebuild.sh 17 Dec 2004 22:25:13 -0000 1.201.2.8 +++ ebuild.sh 2 Jan 2005 07:30:28 -0000 @@ -420,8 +420,10 @@ local -a pref=($(echo ${args/*--prefix[= ]})) CONF_PREFIX=${pref} fi + [ "${CONF_PREFIX:0:1}" != "/" ] && CONF_PREFIX="/${CONF_PREFIX}" + [ "${CONF_LIBDIR:0:1}" != "/" ] && CONF_LIBDIR="/${CONF_LIBDIR}" export CONF_PREFIX - EXTRA_ECONF="--libdir=/${CONF_PREFIX}/${CONF_LIBDIR} ${EXTRA_ECONF}" + EXTRA_ECONF="--libdir=${CONF_PREFIX}${CONF_LIBDIR} ${EXTRA_ECONF}" fi
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.