| 1 |
On Tue, Jul 17, 2018 at 10:48 AM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> W dniu wto, 17.07.2018 o godzinie 10∶40 -0400, użytkownik Mike Gilbert |
| 3 |
> napisał: |
| 4 |
>> On Tue, Jul 17, 2018 at 4:41 AM, Michał Górny <mgorny@g.o> wrote: |
| 5 |
>> > Python 3.5+ introduces parallel build support in distutils. Take |
| 6 |
>> > advantage of that by passing appropriate -j option. Since distutils |
| 7 |
>> > does not support an equivalent of --load-average, default to the number |
| 8 |
>> > of CPUs+1 when unspecified. |
| 9 |
>> |
| 10 |
>> How do we disable this in individual ebuilds when we inevitably run |
| 11 |
>> into problematic packages? |
| 12 |
> |
| 13 |
> My guess would be, same as emake: |
| 14 |
> |
| 15 |
> distutils-r1_python_compile -j1 |
| 16 |
> |
| 17 |
> (I haven't tested it though) |
| 18 |
|
| 19 |
This will affect stable ebuilds that have python3_5 or python3_6 |
| 20 |
enabled. It would be a good idea to test it on a reasonable sample of |
| 21 |
ebuilds first. |
| 22 |
|
| 23 |
Alternatively, we could enable it for python3_7 first and see what |
| 24 |
kind of fallout that produces. |
Archives