| 1 |
Am Mittwoch, 25. Oktober 2006 14:24 schrieb ext Uwe Thiem: |
| 2 |
|
| 3 |
> I am compiling OOO 2.0.4 currently and am somehow surprised. Checking the |
| 4 |
> ebuild shows that it still sets JOBS="1" but it *does* use distcc in my |
| 5 |
> setup. At least parts of OOO are compiled on another box. It never did |
| 6 |
> that before. Did I misread the ebuild? |
| 7 |
|
| 8 |
So how is using distcc and jobs=1 contrary? If you have configured portage |
| 9 |
to use distcc and have distcc configured to only use the remote machine, no |
| 10 |
matter how many jobs yoou start, they will end up on the remote (unless |
| 11 |
distcc itself decides it's not worthwhile). |
| 12 |
|
| 13 |
Bye... |
| 14 |
|
| 15 |
Dirk |
| 16 |
-- |
| 17 |
Dirk Heinrichs | Tel: +49 (0)162 234 3408 |
| 18 |
Configuration Manager | Fax: +49 (0)211 47068 111 |
| 19 |
Capgemini Deutschland | Mail: dirk.heinrichs@×××××××××.com |
| 20 |
Hambornerstraße 55 | Web: http://www.capgemini.com |
| 21 |
D-40472 Düsseldorf | ICQ#: 110037733 |
| 22 |
GPG Public Key C2E467BB | Keyserver: www.keyserver.net |
Archives