The URL above mentions the error and a workaround ("I solved it by setting RANLIB, using export RANLIB=ranlib, before emerging pciutils.") pciutils-2.2.0-r1 does currently not build and finishes with: ... >>> Install pciutils-2.2.0-r1 into /var/tmp/portage/pciutils-2.2.0-r1/image/ category sys-apps make -C lib all make[1]: Entering directory `/var/tmp/portage/pciutils-2.2.0-r1/work/pciutils-2.2.0/lib' i686-pc-linux-gnu-gcc -O2 -Wall -W -Wno-parentheses -Wstrict-prototypes -Wmissing-prototypes -Winline -c -o access.o access.c rm -f libpci.a ar rcs libpci.a access.o generic.o dump.o names.o filter.o sysfs.o proc.o i386-ports.o libpci.a make[1]: libpci.a: Command not found make[1]: *** [libpci.a] Error 127 make[1]: Leaving directory `/var/tmp/portage/pciutils-2.2.0-r1/work/pciutils-2.2.0/lib' make: *** [lib/libpci.a] Error 2 !!! ERROR: sys-apps/pciutils-2.2.0-r1 failed. !!! Function src_install, Line 57, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message.
Compiles fine here, emerge --info, please.
Created attachment 73926 [details] emerge --info Here the 'emerge --info' output you were asking for.
I had a similar problem seems there is a problem with the RANLIB variable: http://forums.gentoo.org/viewtopic-t-403810-highlight-pciutils+libpci.html Ren
I had a similar problem seems there is a problem with the RANLIB variable: http://forums.gentoo.org/viewtopic-t-403810-highlight-pciutils+libpci.html René
You need to reopen the bug once you've provided the requested info, otherwise noone might notice again.
run `emerge --debug pciutils >& log` and post the log as an attachment
Created attachment 74389 [details] Lofile of failed emerge pciutils-2.2.0-r1
same error hiere, here is my emerge info using "RANLIB=ranlib emerge -uv sys-apps/pciutils" worked for me Portage 2.0.51.22-r3 (!/usr/portage/profiles/default-linux/x86/2005.0, gcc-3.3. 6, glibc-2.3.4.20040808-r1,glibc-2.3.5-r2, 2.6.14-hardened-arwen i686) ================================================================= System uname: 2.6.14-hardened-arwen i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.6.13 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 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.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.4.19-r1, 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/ config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe" DISTDIR="/var/distfiles" FEATURES="autoconfig candy ccache distlocks noauto sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.inode.at/ http://gentoo.oregonstate.edu http:// www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="de_AT@euro" LC_ALL="de_AT@euro" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/var/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow acl apache2 bash-completion berkdb crypt gif imap ipv6 jpeg mbox mmx ncurses nls pam png readline shadow spell ssl tcpd tiff xml2 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, LINGUAS, MAKEOPTS
hmm, that stuff shouldnt be running in src_install() which is why it's breaking ... src_compile() properly exported RANLIB if you read the logfile
the makefile looks just dandy to me and it works fine for me ... try running `MAKEOPTS=--debug=b emerge pciutils >& log` and post that logfile as an attachment
Created attachment 74419 [details] output of `MAKEOPTS=--debug=b emerge pciutils >& log` Here the log you were asking for.
err it worked on your machine now ;)
Well, yes you are right, but a 'emerge pciutils' afterwards, still stops with the same old error. What does setting that MAKEOPTS variable do within emerge? Why is it working this way? I guess its an option for make to print debuging output, right? So, well .. I mean .. yes it works, but don't get me wrong, I don't see this as the solution, more as a temporary workaround.
ok, I guess this is going to be a learning experience to me .. I took again a look into the error I was posting at the beginning. It basically removes an existing libpci.a then runs ar .. and then it is screewed because it says: 'make[1]: libpci.a: Command not found' So looked at the tar in my distfile and I think the Makefile in the lib directory has an error at line 52. It says: 'ar rcs $@ $^'. The '^' looks quite odd to me. Could it be, that the person editing this in vi wanted to hit the esc key ;-)
that statement is correct, it's makefile language foo
Same problem here. I have no MAKEOPTS in my make.conf, so i just added MAKEOPTS="-j2" and now, it work...
well ive stared at that log and everything looks right ... the only way that code could have been triggered is if the timestamp of the access.c file was newer than the timestamp of access.o ... someone post a failing log of `MAKEOPTS=--debug=b emerge pciutils >& log`
*** Bug 124528 has been marked as a duplicate of this bug. ***
(In reply to comment #16) > someone post a failing log of `MAKEOPTS=--debug=b emerge pciutils >& log` > Attached as requested. Sometimes I get a clean install and at other times I get the same error as above.
Created attachment 82564 [details] Output of MAKEOPTS=--debug=b emerge pciutils >& log
err, sorry, typo ... i really need: MAKEFLAGS=--debug=b emerge pciutils >& log notice i need MAKEFLAGS, not MAKEOPTS ... MAKEOPTS is ignored in src_install() ...
(In reply to comment #20) > err, sorry, typo ... i really need: > MAKEFLAGS=--debug=b emerge pciutils >& log > > notice i need MAKEFLAGS, not MAKEOPTS ... MAKEOPTS is ignored in src_install() > ... > New log attached as requested.
Created attachment 85213 [details] Output of MAKEFLAGS=--debug=b emerge pciutils >& log
are you guys using tmpfs for /var/tmp/portage ?
(In reply to comment #23) > are you guys using tmpfs for /var/tmp/portage ? I got bitten by this bug also, and the answer is yes. After unmounting the tmpfs compiling didn't fail.
thanks
*** This bug has been marked as a duplicate of 114722 ***
