| 1 |
On Wed, Sep 12, 2012 at 10:00 AM, Alex Schuster <wonko@×××××××××.org> wrote: |
| 2 |
|
| 3 |
> Michael Mol writes: |
| 4 |
> |
| 5 |
> On Wed, Sep 12, 2012 at 9:33 AM, Neil Bothwick <neil@××××××××××.uk |
| 6 |
>> <mailto:neil@××××××××××.uk>> wrote: |
| 7 |
>> |
| 8 |
> |
| 9 |
> Instead we get, try USE="-*" :P |
| 10 |
>> |
| 11 |
>> "Try MAKEOPTS='-j1'" |
| 12 |
>> |
| 13 |
> |
| 14 |
> Which in fact often helps... especially for me, I am using MAKEOPTS="-j |
| 15 |
> --load=4", and I often experience build problems that are not reproducible |
| 16 |
> with a fixed number of jobs, regardless how large. |
| 17 |
> |
| 18 |
|
| 19 |
This can be done on a per-package basis, yet it's inevitably implied I |
| 20 |
should do it in /etc/make.conf instead. |
| 21 |
|
| 22 |
And, really, it's not hard (for me, at least) to repro and/or track down |
| 23 |
the source of parallel-induced build failures; they tend to have a pretty |
| 24 |
clear signature in the build log. If it's a parallel-induced build failure, |
| 25 |
I can look at the log and tell you which target should have had a different |
| 26 |
target as a dependency, but didn't. Last time it happened to me (months |
| 27 |
ago!), everything I needed was in the last twenty lines of build output. |
| 28 |
|
| 29 |
I only wish someone could pay me to do this stuff full-time, because I |
| 30 |
enjoy it. :) |
| 31 |
|
| 32 |
|
| 33 |
> |
| 34 |
> "Turn off distcc" |
| 35 |
>> |
| 36 |
> |
| 37 |
> "revdep-rebuild" |
| 38 |
> |
| 39 |
> And "emerge -e world && perl-cleaner --all && python-updater && |
| 40 |
> lafilefixer --justfixit". |
| 41 |
> |
| 42 |
|
| 43 |
Indeed. And in theory, portage 2.2 (yeah, yeah) should make most of that |
| 44 |
unnecessary. And I think the lafilefixer portion is now a default-enabled |
| 45 |
feature in portage. Not absolutely sure, though. |
| 46 |
|
| 47 |
(And I think you meant perl-cleaner --reallyall :P ) |
| 48 |
|
| 49 |
You should take a look at my gentoo install script and see how many of |
| 50 |
those tidy-up-and-rebuild commands it runs...and then a pair of "emerge -e |
| 51 |
@world" at the end to ensure any build-time dependent creeping changes work |
| 52 |
their way through the entire system. (And that's probably not enough, if |
| 53 |
you're looking for an absolute setup...it'd probably be necessary to |
| 54 |
compare checksums on files between runs and keep building until the setup |
| 55 |
converges...but that'd require being able to ignore anything that includes |
| 56 |
build-time timestamps.) |
| 57 |
|
| 58 |
-- |
| 59 |
:wq |
Archives