Continued from http://bugs.gentoo.org/show_bug.cgi?id=81028#c25. The following is the idea of the problem. Using portage-2.1 (manually installed) I get some more info. When trying to emerge -d pax-utils I get the following error: myaction None myopts ['--debug'] Calculating dependencies Parent: None Depstring: app-misc/pax-utils Candidates: ['app-misc/pax-utils'] ebuild: app-misc/pax-utils-0.1.13 binpkg: None -Parent: ebuild / app-misc/pax-utils-0.1.13 merge Depstring: caps? ( sys-libs/libcap ) caps? ( sys-libs/libcap ) Exiting... None ... done! >>> Emerging (1 of 1) app-misc/pax-utils-0.1.13 to / !!! PORTAGE_WORKDIR_MODE is unset, using 0700. + dyn_clean + '[' -z /var/tmp/portage/pax-utils-0.1.13 ']' + type -p chflags + rm -rf /var/tmp/portage/pax-utils-0.1.13/image /var/tmp/portage/pax-utils-0.1.13/homedir + hasq keeptemp autoconfig distlocks sandbox sfperms strict + [[ autoconfig distlocks sandbox sfperms strict == *\ \k\e\e\p\t\e\m\p\ * ]] + rm -rf /var/tmp/portage/pax-utils-0.1.13/temp + hasq keepwork autoconfig distlocks sandbox sfperms strict + [[ autoconfig distlocks sandbox sfperms strict == *\ \k\e\e\p\w\o\r\k\ * ]] + rm -rf /var/tmp/portage/pax-utils-0.1.13/.unpacked + rm -rf /var/tmp/portage/pax-utils-0.1.13/.compiled + rm -rf /var/tmp/portage/pax-utils-0.1.13/.tested + rm -rf /var/tmp/portage/pax-utils-0.1.13/.installed + rm -rf /var/tmp/portage/pax-utils-0.1.13/.packaged + rm -rf /var/tmp/portage/pax-utils-0.1.13/build-info + rm -rf /var/tmp/portage/pax-utils-0.1.13/work + '[' -f /var/tmp/portage/pax-utils-0.1.13/.unpacked ']' + rm -rf /var/tmp/portage/pax-utils-0.1.13/distdir ++ find /var/tmp/portage/pax-utils-0.1.13 -mindepth 1 -maxdepth 1 + '[' -z '' ']' + rmdir /var/tmp/portage/pax-utils-0.1.13 + true + set +x !!! PORTAGE_WORKDIR_MODE is unset, using 0700. >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking pax-utils-0.1.13.tar.bz2 ;-) + dyn_setup ++ type -t pre_pkg_setup + '[' '' == function ']' + pkg_setup + return ++ type -t post_pkg_setup + '[' '' == function ']' + set +x Does this ring any bells with anyone?
(In reply to comment #0) > !!! PORTAGE_WORKDIR_MODE is unset, using 0700. BTW, that message means you need to update /etc/make.globals (from the cnf directory of portage-2.1.tar.bz2). Please attach the --debug output with FEATURES="python-trace" enabled.
Since the file is 6.3MB big, hosted it here[1] instead of uploading. 1: http://il.fontys.nl/~ruud/misc/emerge_pax-utils_20060630.log
portage_exec.py line=201 name=spawn event=return value=3328 locals={'fd_pipes': {0: 0, 1: 1, 2: 2}, 'mycommand': ['/usr/bin/sandbox', '/usr/lib/portage/bin/ebuild.sh unpack'], 'logfile': None, 'uid': None, 'binary': '/usr/bin/sandbox', 'pid': 23309, 'opt_name': '[pax-utils-0.1.13] sandbox', 'returnpid': False, 'umask': None, 'path_lookup': True, 'gid': None, 'mypids': [], 'env': 'omitted', 'groups': None, 'retval': 13} That 3328 return value translates to SIGPIPE. Please post the output of `emerge --info`.
!!! No gcc found. You probably need to 'source /etc/profile' !!! to update the environment of this terminal and possibly !!! other terminals also. Portage 2.1 (default-linux/x86/2006.0, [unavailable], glibc-2.3.6-r3, 2.6.15.5 i686) ================================================================= System uname: 2.6.15.5 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 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 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf" CXXFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X a52 aac acpi aim avi berkdb bitmap-fonts browserplugin cli crypt cups dri eds emboss encode esd foomaticdb fortran gdbm gif gimpprint glibc-omitfp gnome gpgme gstreamer gtk gtk2 icq imap imlib ipv6 irc isdnlog jabber javascript jpeg kde libg++ libwww live mad mbox mikmod mmx mmxext motif mozsvg mp3 mpeg msn ncurses nls nntp nptl nptlonly nsplugin ogg pam pascal pcre pdflib perl php png pop ppds pppd python qt qt3 qt4 quicktime readline real reflection rtc sdl session smime spell spl sql sse ssl subversion tcpd tga theora threads truetype truetype-fonts type1-fonts udev unicode utf8 vcd vorbis win32codecs xml xorg xprint zlib elibc_glibc kernel_linux userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY The gcc error is odd since it is installed (2 of 'm) and gcc-config -l shows that a profile is selected.
What results do you get for the following commands: cd /usr/portage/app-misc/pax-utils FEATURES=-sandbox PORTAGE_DEBUG=1 ebuild pax-utils-0.1.13.ebuild unpack
>>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking pax-utils-0.1.13.tar.bz2 ;-) + dyn_setup ++ type -t pre_pkg_setup + '[' '' == function ']' + pkg_setup + return ++ type -t post_pkg_setup + '[' '' == function ']' + set +x + dyn_unpack + trap abort_unpack SIGINT SIGQUIT ++ type -t pre_src_unpack + '[' '' == function ']' + local newstuff=no + '[' -e /var/tmp/portage/pax-utils-0.1.13/work ']' + local x + local checkme + for x in '${AA}' + vecho '>>> Checking pax-utils-0.1.13.tar.bz2'\''s mtime...' + [[ '' == \1 ]] + echo '>>> Checking pax-utils-0.1.13.tar.bz2'\''s mtime...' >>> Checking pax-utils-0.1.13.tar.bz2's mtime... + '[' /usr/portage/distfiles/pax-utils-0.1.13.tar.bz2 -nt /var/tmp/portage/pax-utils-0.1.13/work ']' + '[' /usr/portage/app-misc/pax-utils/pax-utils-0.1.13.ebuild -nt /var/tmp/portage/pax-utils-0.1.13/work ']' + '[' '!' -f /var/tmp/portage/pax-utils-0.1.13/.unpacked ']' + '[' -e /var/tmp/portage/pax-utils-0.1.13/work ']' + '[' no == no ']' + vecho '>>> WORKDIR is up-to-date, keeping...' + [[ '' == \1 ]] + echo '>>> WORKDIR is up-to-date, keeping...' >>> WORKDIR is up-to-date, keeping... ++ type -t post_src_unpack + '[' '' == function ']' + return 0 + set +x
Okay, so you were able to unpack it using the commands from comment #5. So, somethings different there, because the unpack phase fails when you run emerge. Can you try to unpack it with sandbox enabled and see if it still works? FEATURES=sandbox PORTAGE_DEBUG=1 ebuild pax-utils-0.1.13.ebuild unpack
>>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking pax-utils-0.1.13.tar.bz2 ;-) + dyn_setup ++ type -t pre_pkg_setup + '[' '' == function ']' + pkg_setup + return ++ type -t post_pkg_setup + '[' '' == function ']' + set +x + dyn_unpack + trap abort_unpack SIGINT SIGQUIT ++ type -t pre_src_unpack + '[' '' == function ']' + local newstuff=no + '[' -e /var/tmp/portage/pax-utils-0.1.13/work ']' + '[' -e /var/tmp/portage/pax-utils-0.1.13/work ']' + '[' '!' -d /var/tmp/portage/pax-utils-0.1.13/work ']' + install -m0700 -d /var/tmp/portage/pax-utils-0.1.13/work + cd /var/tmp/portage/pax-utils-0.1.13/work + vecho '>>> Unpacking source...' + [[ '' == \1 ]] + echo '>>> Unpacking source...' >>> Unpacking source... + src_unpack + unpack pax-utils-0.1.13.tar.bz2 + local x + local y + local myfail + local tarvars + '[' GNU == BSD ']' + tarvars=--no-same-owner + '[' -z pax-utils-0.1.13.tar.bz2 ']' + for x in '"$@"' + vecho '>>> Unpacking pax-utils-0.1.13.tar.bz2 to /var/tmp/portage/pax-utils-0.1.13/work' + [[ '' == \1 ]] + echo '>>> Unpacking pax-utils-0.1.13.tar.bz2 to /var/tmp/portage/pax-utils-0.1.13/work' >>> Unpacking pax-utils-0.1.13.tar.bz2 to /var/tmp/portage/pax-utils-0.1.13/work+ y=pax-utils-0.1.13.tar + y=tar + myfail='pax-utils-0.1.13.tar.bz2 does not exist' + '[' pa = ./ ']' + srcdir=/var/tmp/portage/pax-utils-0.1.13/distdir/ + [[ pax-utils-0.1.13.tar.bz2 == /var/tmp/portage/pax-utils-0.1.13/distdir* ]] + '[' '!' -s /var/tmp/portage/pax-utils-0.1.13/distdir/pax-utils-0.1.13.tar.bz2 ']' + myfail='failure unpacking pax-utils-0.1.13.tar.bz2' + case "${x##*.}" in + '[' tar == tar ']' + bzip2 -dc /var/tmp/portage/pax-utils-0.1.13/distdir/pax-utils-0.1.13.tar.bz2 + tar xf - --no-same-owner + _pipestatus='0 0' + [[ 00 -eq 0 ]] + chmod -Rf a+rX,u+w,g-w,o-w . + cd /var/tmp/portage/pax-utils-0.1.13/work/pax-utils-0.1.13 + touch /var/tmp/portage/pax-utils-0.1.13/.unpacked + vecho '>>> Source unpacked.' + [[ '' == \1 ]] + echo '>>> Source unpacked.' >>> Source unpacked. + cd /var/tmp/portage/pax-utils-0.1.13 ++ type -t post_src_unpack + '[' '' == function ']' + trap SIGINT SIGQUIT + set +x
In both cases, the unpack phase succeeded. When emerge fails, does it always fail at the unpack phase with the same exit code? What do you get for the following: FEATURES=-sandbox emerge =pax-utils-0.1.13 echo $?
Yes, I always get it exiting to prompt. And the exitcode was '0'.
(In reply to comment #10) > Yes, I always get it exiting to prompt. And the exitcode was '0'. That doesn't match the log referenced in comment #2. In that case the unpack phase seemed to be killed by a SIGPIPE, resulting in an exitcode of 3328. That log is useless since it didn't exit in exactly the same way. Can you try to create another --debug log with FEATURES="python-trace" enabled? The log should contain a SystemExit exception with the same '0' value that you've just reported.
If you mean "FEATURES=python-trace ebuild --debug pax-utils-0.1.13.ebuild unpack" you can find the output here[1]. 1: http://il.fontys.nl/~ruud/misc/ebuild_unpack_pax-utils_20060703.log
(In reply to comment #12) > If you mean "FEATURES=python-trace ebuild --debug pax-utils-0.1.13.ebuild > unpack" That's not what I meant. I need you to reproduce the emerge problem and give me the debug output. Something like this: FEATURES="python-trace" emerge --debug pax-utils The log mentioned in comment #2 is useless because it did not exit with status 0 as you've reported.
Bug 147625 seems similar. It has the same "No gcc found" message and 3328 error code.
reopen for duping
*** This bug has been marked as a duplicate of bug 147625 ***
