| 1 |
Nuno Silva wrote: |
| 2 |
> On 2022-11-30, Jochen Kirchner wrote: |
| 3 |
> |
| 4 |
> [...] |
| 5 |
>> make -j17 -l17 VERBOSE=true OPTFLAGS= CXX=x86_64-pc-linux-gnu-g++ |
| 6 |
> Can you try emerging with -j1 in MAKEOPTS? |
| 7 |
> |
| 8 |
> Sadly, the makefile[1] does not print out the mkdir commands (recipe on |
| 9 |
> lines 202 thru 204), so it's not possible to spot in the output when are |
| 10 |
> these being executed, but, from a quick glance (I might have overlooked |
| 11 |
> something!), it sounds like the target that runs mkdir is not a |
| 12 |
> dependency of the targets that generate and link the object files (line |
| 13 |
> 262, line 273), so it'd be possible for this to happen just because |
| 14 |
> the second mkdir did not complete before the first g++ was checking for |
| 15 |
> the directory. |
| 16 |
> |
| 17 |
> [1] https://github.com/aristocratos/btop/blob/main/Makefile |
| 18 |
> |
| 19 |
|
| 20 |
|
| 21 |
That's a good idea. Just to test if that error happens to everybody, I |
| 22 |
installed btop-1.2.12 here. Actually, it's kinda neat looking. Anyway, |
| 23 |
it installed fine here on my 8 core machine with normal -j settings, -j9 |
| 24 |
I think. It could help using -j1 tho. Still, it installed here without |
| 25 |
any problems. |
| 26 |
|
| 27 |
If -j1 doesn't work, maybe sync the tree again to see if maybe some typo |
| 28 |
got fixed or something else was wrong during last sync. That is rare |
| 29 |
nowadays but when grasping at straws, grab what you can. |
| 30 |
|
| 31 |
Oh, my google search earlier didn't yield anything either. This seems |
| 32 |
to be a odd failure. |
| 33 |
|
| 34 |
Dale |
| 35 |
|
| 36 |
:-) :-) |
Archives