public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Haskell packages and keeptemp
Date: Mon, 21 Sep 2015 08:55:37 +0200	[thread overview]
Message-ID: <55FFA9E9.5050907@gmail.com> (raw)
In-Reply-To: <20150921064157.GA13957@mikasa>

On 21/09/2015 08:41, Bryan Gardiner wrote:
> On Mon, Sep 21, 2015 at 07:29:39AM +0200, J. Roeleveld wrote:
>> On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@khumba.net> wrote:
>>> Hi gentoo-users,
>>>
>>> I thought I would set FEATURES=keeptemp in make.conf so I would have
>>> build logs around for reference.  This causes problems with Haskell
>>> packages, which fail during the second build after setting this,
>>> because the build's temp/ hasn't been cleaned from the previous build:
>>>
>>> <snip>
>>>
>>> Am I wrong in expecting ${T} to be wiped at the start of a build,
>>> regardless of the package, so that this isn't a problem?  I'm not sure
>>> why you'd want old temp/ state to carry forward to the next build.
>>>
>>> - Bryan
>>
>> Build logs usually (I didn't change anything for that) end up in
>> /var/log/portage
>>
>> Did you check there?
> 
> All I have there is /var/log/portage/elog which is because I
> explicitly added "save" to PORTAGE_ELOG_SYSTEM.  I want the build.log
> files, not just the elog output, do you have those in
> /var/log/portage?

That's not quite what PORTAGE_ELOG_SYSTEM does. That is for elogs, not
build logs. You need this:

PORT_LOGDIR=/var/log/portage


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2015-09-21  6:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  3:58 [gentoo-user] Haskell packages and keeptemp Bryan Gardiner
2015-09-21  4:29 ` Michael Orlitzky
2015-09-21  5:03   ` Bryan Gardiner
2015-09-21  5:29 ` J. Roeleveld
2015-09-21  6:41   ` Bryan Gardiner
2015-09-21  6:55     ` Alan McKinnon [this message]
2015-09-21 15:37       ` Bryan Gardiner

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=55FFA9E9.5050907@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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