| 1 |
Quoting Pat Double <double@×××××××××.com>: |
| 2 |
|
| 3 |
> Perhaps I am mistaken. In previous versions of portage that supported |
| 4 |
> distcc, I would find the compiler command reported in ./configure as |
| 5 |
> "distcc gcc". Is this the case with portage-2.0.47-r7? Or is it done |
| 6 |
> through the path somehow? I noticed that I have been getting hangs in |
| 7 |
> compiling this morning (I thought maybe due to the new glibc), so I |
| 8 |
> tried setting MAKEOPTS="-j1" and the problem when away. Not satisified |
| 9 |
> it is glibc, I removed "distcc" as a FEATURE and the problem is gone. |
| 10 |
|
| 11 |
I had problems building glibc with distcc in the past (it would segfault |
| 12 |
when linking something -- can't remember what). Aside from this, you can |
| 13 |
watch your logs on the distccd machines (whatever you have the daemon |
| 14 |
facility pointing to in your syslog configuration -- /var/log/daemon.log by |
| 15 |
default). You should see that log moving whenever you're building |
| 16 |
something via portage. You *won't* see "distcc gcc" in the make process |
| 17 |
because the distcc FEATURE rewrites the path with /usr/lib/distcc/bin as |
| 18 |
the first item where links for all gcc binaries exist pointing to distcc -- |
| 19 |
making it very transparent. In any case...it is probably better to build |
| 20 |
glibc without distcc; other than that, everything else worked fine for me. |
| 21 |
|
| 22 |
|
| 23 |
---max kalika |
| 24 |
--max@×××××××××.edu |
| 25 |
-lsit systems administrator |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives