Re: [gentoo-user] emerging squid indefinitely

[Alan McKinnon <alan.mckinnon@gmail.com>]

On 23/11/2015 23:04, lee wrote:
> 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 ...
> 


the build logs are the same place they have always been, in
/var/tmp/portage/.....

that location is a symlink to:

/var/log/portage/<cat>:<pkg>-<ver>:<timestamp>.log

and that info is dumped to the console in volume every time emerge fails
for any reason.

/var/log/portage/elog/summary.log and /var/log/emerge.log are emerge's
logs and contains logs of what emerge is doing. You want build logs to
find out what make and gcc etc are doing.


-- 
Alan McKinnon
alan.mckinnon@gmail.com