Bug 68868 – cannot emerge libwww-5.4.0-r2 due to an error during src_install function

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Marius 2004-10-25 11:02:48 UTC]

Cannot emerge libwww-5.4.0-r2, the error is the instruction:

test -z "/usr/bin" ||  "/var/tmp/portage/libwww-5.4.0-r2/image//usr/bin"
/bin/sh: line 1: /var/tmp/portage/libwww-5.4.0-r2/image//usr/bin: is a directory


here an extract of the complete result:

make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0/Icons'
make[3]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0/Icons'
make[2]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0/Icons'
make[2]: Entering directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0'
make[3]: Entering directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0'
test -z "/usr/bin" ||  "/var/tmp/portage/libwww-5.4.0-r2/image//usr/bin"
/bin/sh: line 1: /var/tmp/portage/libwww-5.4.0-r2/image//usr/bin: is a directory
make[3]: *** [install-binSCRIPTS] Error 126
make[3]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0'
make: *** [install] Error 2

!!! ERROR: net-libs/libwww-5.4.0-r2 failed.
!!! Function src_install, Line 71, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.


Reproducible: Always
Steps to Reproduce:




Portage 2.0.51-r2 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.2-r9,
2.4.25-gentoo-r1 i686)
=================================================================
System uname: 2.4.25-gentoo-r1 i686 AMD Athlon(tm) XP 1600+
Gentoo Base System version 1.4.3.13
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.4.3-r4
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
CHOST="i686-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/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="http://mir.zyrianes.net/gentoo/ ftp://mir.zyrianes.net/gentoo/
ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups doc encode esd
f77 foomaticdb gdbm gif gnome gpm gtk gtk2 guile imlib java jpeg kde ldap libg++
libwww mad mikmod mmx motif mozilla mpeg ncurses nls no_wxgtk1 oggvorbis opengl
oss pam pdflib perl png python qt quicktime readline sdl slang spell sse ssl
svga tcltk tcpd threads truetype x86 xml2 xmms xprint xv zlib"

[Comment 1 Mamoru KOMACHI (RETIRED) 2004-10-26 22:18:10 UTC]

I cannot reproduce the error. What's the content of 
/var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0/Makefile
(please post it as an attachment)?

[Comment 2 Marius 2004-10-28 07:36:33 UTC]

Created attachment 42774 [details]
The content of /var/tmp/portage/libwww-5.4.0-r2/work/w3c-libwww-5.4.0/Makefile

Here it is the Makefile.

[Comment 3 Mamoru KOMACHI (RETIRED) 2004-10-28 08:28:01 UTC]

Thanks. It looks $(mkdir_p) is not defined 
in your Makefile (automake-1.5 should be
used here but automake-1.8.5 is used in
your environment).

btw, you have autoconf-2.58-r1 installed but
our Portage has only 2.59-r5 for stable environment.
Does emerging autoconf-2.59-r5 (and remerge automake)
solve the problem?

[Comment 4 Marius 2004-10-29 10:23:16 UTC]

I emerged autoconf-2.59-r5 and the problem remained.
I reemerged manually automake and the problem was solved :) 

[Comment 5 Mamoru KOMACHI (RETIRED) 2004-10-30 01:06:57 UTC]

Thanks for the test. We are in transition from
autoconf to autoconf-wrapper plus SLOT'ed autoconf,
and it might have been broken at some point.