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