| 1 |
On Jul 11, 2005, at 7:32 AM, Henrik Brix Andersen wrote: |
| 2 |
|
| 3 |
> On Mon, 2005-07-11 at 14:20 +0200, Diego 'Flameeyes' Pettenò wrote: |
| 4 |
> |
| 5 |
>> Let's see: we already have an emake script, but using it for "make |
| 6 |
>> install" is |
| 7 |
>> a no-go because it uses -jX from make.conf and that's not good. |
| 8 |
>> A solution can be to improve emake wrapper to check if "install" |
| 9 |
>> is in its |
| 10 |
>> commandline, in which case it can automatically add a -j1 to be safe. |
| 11 |
>> |
| 12 |
> |
| 13 |
> What is the problem with using -jX for `make install`? |
| 14 |
> |
| 15 |
|
| 16 |
THink about what happens in most `make install` phases, files get put |
| 17 |
in their DESTROOT, and many times permissions are set etc. when its |
| 18 |
done in parallel the chances of the makefile trying to operate on non- |
| 19 |
existent targets is quite high, and things start to explode. |
| 20 |
|
| 21 |
> Regards, |
| 22 |
> Brix |
| 23 |
> -- |
| 24 |
> Henrik Brix Andersen <brix@g.o> |
| 25 |
> Gentoo Metadistribution | Mobile computing herd |
| 26 |
> |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives