After upgrading to Portage 2.0.51_rc6, emerge will just download the tarball, then sit there without doing anything: % sudo emerge nano Calculating dependencies ...done! >>> emerge (1 of 1) app-editors/nano-1.3.4 to / >>> Downloading http://gentoo.osuosl.org/distfiles/nano-1.3.4.tar.gz ######################################################################## 100.0% >>> md5 src_uri ;-) nano-1.3.4.tar.gz Reproducible: Always Steps to Reproduce: 1. emerge SOME_PACKAGE 2. 3. Actual Results: the tarball was downloaded into /var/tmp/portage and gunzipped, but not compiled. Expected Results: source should have been compiled. manual compilation (configure, make, make install) works flawlessly.
Did it fail? Did it sleep? emerge -d What processes are running?
No, it completed without errors. Here's the output from emerge -d: % sudo emerge -d nano Password: Calculating dependencies Parent: None Depstring: app-editors/nano Candidates: ['app-editors/nano'] ebuild: app-editors/nano-1.3.4 binpkg: None - Parent: ebuild / app-editors/nano-1.3.4 merge Depstring: >=sys-libs/ncurses-5.2 nls? ( sys-devel/gettext ) slang? ( sys-libs/slang ) !bootstrap? ( sys-devel/patch ) >=sys-libs/ncurses-5.2 nls? ( sys-devel/gettext ) slang? ( sys-libs/slang ) Candidates: [] Exiting... ebuild / app-editors/nano-1.3.4 merge Exiting... None ...done! >>> emerge (1 of 1) app-editors/nano-1.3.4 to / + dyn_clean + rm -rf /var/tmp/portage/nano-1.3.4/image + hasq keeptemp autoaddcvs ccache collision-protect cvs distlocks keepwork sandbox + local x + local me=keeptemp + shift + '[' autoaddcvs == keeptemp ']' + '[' ccache == keeptemp ']' + '[' collision-protect == keeptemp ']' + '[' cvs == keeptemp ']' + '[' distlocks == keeptemp ']' + '[' keepwork == keeptemp ']' + '[' sandbox == keeptemp ']' + return 1 + rm -rf /var/tmp/portage/nano-1.3.4/temp/eclass-debug.log + hasq keepwork autoaddcvs ccache collision-protect cvs distlocks keepwork sandbox + local x + local me=keepwork + shift + '[' autoaddcvs == keepwork ']' + '[' ccache == keepwork ']' + '[' collision-protect == keepwork ']' + '[' cvs == keepwork ']' + '[' distlocks == keepwork ']' + '[' keepwork == keepwork ']' + return 0 + '[' -f /var/tmp/portage/nano-1.3.4/.unpacked ']' + find /var/tmp/portage/nano-1.3.4 -type d '!' -regex '^/var/tmp/portage/nano-1.3.4/work' + sort -r + tr '\n' '\0' + xargs -0 rmdir + true + set +x >>> md5 src_uri ;-) nano-1.3.4.tar.gz + dyn_setup + '[' BSD == Linux ']' + pkg_setup + return + set +x I tried several times, with different processes running.
Add -sandbox to the FEATURES in /etc/make.conf
he doesnt have sandbox in FEATURES i dont think you did neglect to provide `emerge info` like the bug report page says to try removing all the directories in /var/tmp/portage/ and see if that helps
Problem seems to be resolved. My apologies for the long post, but I tried to follow all the advice. Unfortunately, I am not sure which step slved the problem. I downgraded to an older version of portage (from the latest gentoo-macos-20040726.dmg): Portage 20040726 (default-macos-10.3, gcc-3.3, unavailable, 7.5.0 Power Macintosh powerpc) ================================================================= System uname: 7.5.0 Power Macintosh powerpc macos-20040726 distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.57 Automake: sys-devel/automake-1.6.3 Binutils: ACCEPT_KEYWORDS="macos" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="powerpc-apple-darwin" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="collision-protect cvs keepwork" GENTOO_MIRRORS="http://gentoo.osuosl.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="macos berkdb ldap mysql perl python ruby" Result: emerge nano compiles fine (nano is just an example; it's the same with other ebuilds). Added -sandbox to /etc/make.conf. Ran emerge sync. Emerged portage update: Portage 2.0.51_rc6 (default-macos-10.3, gcc-3.3, libsystem-7.1-r0, 7.5.0 Power Macintosh) ================================================================= System uname: 7.5.0 Power Macintosh powerpc macos-20040726 distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.57 Automake: sys-devel/automake-1.6.3 Binutils: Headers: Libtools: sys-devel/libtool-2.4.4 ACCEPT_KEYWORDS="macos ~ppc-macos" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="powerpc-apple-darwin" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="collision-protect cvs keepwork" GENTOO_MIRRORS="http://gentoo.osuosl.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="macos berkdb ldap mysql perl python ruby" Now emerge appears to be working. Thx for the help!
i was able to reproduce this ... basically it's either a problem with your bash and/or sandbox ... if something is causing bash+sandbox to segfault, you'll see this odd output ... check dmesg and try running `/usr/lib/portage/bin/sandbox` ... if sandbox exits without starting up a shell, then it's because the combination is segfaulting
Closing due to old age
