From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] More emerge oddity in chroot
Date: Fri, 09 May 2014 00:34:20 +0100 [thread overview]
Message-ID: <1705870.juBmpdkTIZ@wstn> (raw)
In-Reply-To: <5383625.3zvFPHoqv2@wstn>
On Thursday 24 April 2014 13:57:19 Peter Humphrey wrote:
> Hello list,
>
> I'm wearying of this chroot operation, and I must be sounding like a tyro.
>
> The other day emerge started hanging at the end of compilation, thus:
>
> # emerge -1 apache-tools
[,,,]
> >>> Completed installing apache-tools-2.2.25 into /var/tmp/portage/app-
>
> admin/apache-tools-2.2.25/image/
>
> strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment -R
> .GCC.command.line -R .note.gnu.gold-version
> usr/sbin/htpasswd
> usr/sbin/ab
> usr/sbin/rotatelogs
> usr/sbin/logresolve
> usr/sbin/htdigest
> usr/sbin/htdbm
> usr/sbin/htcacheclean
> usr/sbin/httxt2dbm
> usr/sbin/checkgid
>
> >>> Done.
>
> It never comes back from there, not even with a CTRL-C; I have to "kill -9"
> from another Konsole.
I've found what was causing this. I can hardly believe it myself, but the
evidence is conclusive.
In my /etc/init.d/atom start script I nfs-mounted the Atom's package
directory, but for historical reasons (latterly approaching the hysterical) I
was passing "-o vers=3". Once I removed that, portage sprang back into life.
Go figure, as they say on the other side of the pond.
--
Regards
Peter
prev parent reply other threads:[~2014-05-08 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 12:57 [gentoo-user] More emerge oddity in chroot Peter Humphrey
2014-04-24 21:05 ` Philip Webb
2014-04-25 8:16 ` Peter Humphrey
2014-04-28 12:32 ` Peter Humphrey
2014-04-29 0:47 ` [gentoo-user] More emerge oddity in chroot - SOLVED Peter Humphrey
2014-05-04 18:52 ` J. Roeleveld
2014-05-05 9:17 ` Peter Humphrey
2014-05-08 23:34 ` Peter Humphrey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1705870.juBmpdkTIZ@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox