From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerging squid indefinitely
Date: Mon, 23 Nov 2015 17:12:53 -0500 [thread overview]
Message-ID: <20151123221253.GF3539@ns1.bonedaddy.net> (raw)
In-Reply-To: <87d1v0e8be.fsf@heimdali.yagibdah.de>
* lee <lee@yagibdah.de> [151123 16:05]:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
>
> > On 23/11/2015 17:02, lee wrote:
> >>
> >> Hi,
> >>
> >> emerging squid doesn't seem to ever finish:
> >>
> >>
> >> [...]
> >>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
> >>>>> Jobs: 8 of 9 complete, 1 running Load avg: 0.37, 0.61, 0.53
> >>
> >>
> >> What would I look at, without interrupting emerge, to find out what's
> >> going on?
> >>
> >
> >
> > tail the build log
>
> Which is where? There isn't anything in
> /var/log/portage/elog/summary.log, and /var/log/emerge.log only says:
>
>
> 1448288177: ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to /
> 1448288177: >>> emerge (9 of 9) net-proxy/squid-3.5.6 to /
> 1448288177: === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
> 1448288177: === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
>
>
> It's still pretending that it's compiling, hours later ...
It should be at /var/tmp/portage/net-proxy/squid-3.5.6/temp/build.log.
Todd
next prev parent reply other threads:[~2015-11-23 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:02 [gentoo-user] emerging squid indefinitely lee
2015-11-23 15:25 ` Alan McKinnon
2015-11-23 21:04 ` lee
2015-11-23 22:12 ` Todd Goodman [this message]
2015-11-23 22:28 ` Alan McKinnon
2015-11-24 22:39 ` lee
2015-11-25 0:32 ` [gentoo-user] " walt
2015-11-25 11:30 ` lee
2015-11-25 16:53 ` Alan McKinnon
2015-11-25 23:33 ` lee
2015-11-26 7:58 ` Alan McKinnon
2015-11-26 0:03 ` walt
2015-11-26 7:57 ` Alan McKinnon
2015-11-26 9:48 ` Peter Humphrey
2015-11-26 11:22 ` waltdnes
2015-11-26 17:35 ` J. Roeleveld
2015-11-26 9:51 ` Neil Bothwick
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=20151123221253.GF3539@ns1.bonedaddy.net \
--to=tsg@bonedaddy.net \
--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