| 1 |
On 21/09/2015 08:41, Bryan Gardiner wrote: |
| 2 |
> On Mon, Sep 21, 2015 at 07:29:39AM +0200, J. Roeleveld wrote: |
| 3 |
>> On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@××××××.net> wrote: |
| 4 |
>>> Hi gentoo-users, |
| 5 |
>>> |
| 6 |
>>> I thought I would set FEATURES=keeptemp in make.conf so I would have |
| 7 |
>>> build logs around for reference. This causes problems with Haskell |
| 8 |
>>> packages, which fail during the second build after setting this, |
| 9 |
>>> because the build's temp/ hasn't been cleaned from the previous build: |
| 10 |
>>> |
| 11 |
>>> <snip> |
| 12 |
>>> |
| 13 |
>>> Am I wrong in expecting ${T} to be wiped at the start of a build, |
| 14 |
>>> regardless of the package, so that this isn't a problem? I'm not sure |
| 15 |
>>> why you'd want old temp/ state to carry forward to the next build. |
| 16 |
>>> |
| 17 |
>>> - Bryan |
| 18 |
>> |
| 19 |
>> Build logs usually (I didn't change anything for that) end up in |
| 20 |
>> /var/log/portage |
| 21 |
>> |
| 22 |
>> Did you check there? |
| 23 |
> |
| 24 |
> All I have there is /var/log/portage/elog which is because I |
| 25 |
> explicitly added "save" to PORTAGE_ELOG_SYSTEM. I want the build.log |
| 26 |
> files, not just the elog output, do you have those in |
| 27 |
> /var/log/portage? |
| 28 |
|
| 29 |
That's not quite what PORTAGE_ELOG_SYSTEM does. That is for elogs, not |
| 30 |
build logs. You need this: |
| 31 |
|
| 32 |
PORT_LOGDIR=/var/log/portage |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Alan McKinnon |
| 37 |
alan.mckinnon@×××××.com |
Archives