I get the same failure with jpeg-6b-r4 and -r5. QA Notice: the following files contain insecure RUNPATH's Please file a bug about this at http://bugs.gentoo.org/ For more information on this issue, kindly review: http://bugs.gentoo.org/81745 /var/tmp/portage/jpeg-6b-r4/image//usr/lib usr/bin/cjpeg /var/tmp/portage/jpeg-6b-r4/image//usr/lib usr/bin/djpeg /var/tmp/portage/jpeg-6b-r4/image//usr/lib usr/bin/jpegtran !!! ERROR: media-libs/jpeg-6b-r4 failed. !!! Function dyn_install, Line 1057, Exitcode 0 !!! Insecure binaries detected !!! If you need support, post the topmost build error, NOT this status message. maria ~ # emerge info Portage 2.0.54 (default-linux/alpha/no-nptl/2.4, gcc-3.3.2, glibc-2.3.5-r3, 2.4.32 alpha) ================================================================= System uname: 2.4.32 alpha EV5 Gentoo Base System version 1.6.14 distcc 2.18.3 alpha-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5, 2.4.2 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.4.23 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-mieee -O3 -mcpu=ev5 -pipe -fkeep-inline-functions -frename-registers" CHOST="alpha-unknown-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="-mieee -O3 -mcpu=ev5 -pipe -fkeep-inline-functions -frename-registers" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks noauto 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" SYNC="rsync://192.168.1.2/gentoo-portage" USE="alpha X Xaw3d alsa apache2 arts audiofile bash-completion berkdb bitmap-fonts bzip2 crypt cups dlloader dmx eds encode esd expat fam foomaticdb fortran gdbm gif glitz gnome gnutls gpm gstreamer gtk gtk2 hpn imlib insecure-drivers ipv6 justify kde libedit libg++ libwww mad mailwrapper mikmod motif mp3 mpeg nas ncurses nls ogg opengl oss pam pam_console pcre pdflib png python qt quicktime readline sdl sftplogging spell ssl symlink tcpd toolbar truetype truetype-fonts type1-fonts udev usb vorbis xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
post a full emerge log: emerge jpeg >& log
Created attachment 81273 [details] Log of an emerge attempt
looks like your host is broken or something: >>> Install jpeg-6b-r5 into /var/tmp/portage/jpeg-6b-r5/image/ category media-libs libtool --mode=compile alpha-unknown-linux-gnu-gcc -mieee -O2 -mcpu=ev5 -pipe -I. -c ./jcapimin.c alpha-unknown-linux-gnu-gcc -mieee -O2 -mcpu=ev5 -pipe -I. -c ./jcapimin.c -fPIC -DPIC -o .libs/jcapimin.o alpha-unknown-linux-gnu-gcc -mieee -O2 -mcpu=ev5 -pipe -I. -c ./jcapimin.c -o jcapimin.o >/dev/null 2>&1 try this: MAKEOPTS="-j1" MAKEFLAGS="--debug=b" emerge jpeg >& log and then post the log as an attachment
Created attachment 81512 [details] Log with more make stuff
is your clock broken ? the reason stuff is rebuilt in src_install is that make thinks jconfig.h is newer than all the generated objects when it shouldnt be what does this show: export FEATURES=-noauto ebuild /usr/portage/media-libs/jpeg/jpeg-6b-r5.ebuild compile >& log ls -l /var/tmp/portage/jpeg-6b-r6/work/jpeg-6b/ >> log
Created attachment 81547 [details] List of files As far as I know my clock is fine - it shows the proper time, which is all I really know to test - but I agree make seems to think jconfig.h is newer than it should be. export FEATURES=-noauto doesn't seem to have had any effect as far as I can see - do you want me to do it again with -noauto in make.conf?
Something I've just remembered which could possibly be related: /var/tmp/portage is on NFS. Looking at that listing all the timestamps seem to be correct, but could this be affecting things?
> Something I've just remembered which could possibly be related: > /var/tmp/portage is on NFS. Looking at that listing all the timestamps seem to > be correct, but could this be affecting things? it could be ... please try unmounting it and building jpeg on a "normal" local fs
Yes, that was it, sorry. Resolve invalid?
sounds good
