Re: [gentoo-dev] portage-2.0.47-r6 and distcc

[Pat Double]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 28 February 2003 08:54 am, Max Kalika wrote:
> Quoting Pat Double <double@×××××××××.com>:
> > Perhaps I am mistaken. In previous versions of portage that supported
> > distcc,  I would find the compiler command reported in ./configure as
> > "distcc gcc". Is  this the case with portage-2.0.47-r7? Or is it done
> > through the path somehow?  I noticed that I have been getting hangs in
> > compiling this morning (I thought  maybe due to the new glibc), so I
> > tried setting MAKEOPTS="-j1" and the  problem when away. Not satisified
> > it is glibc, I removed "distcc" as a  FEATURE and the problem is gone.
>
> I had problems building glibc with distcc in the past (it would segfault
> when linking something -- can't remember what).  Aside from this, you can
> watch your logs on the distccd machines (whatever you have the daemon
> facility pointing to in your syslog configuration -- /var/log/daemon.log by
> default).  You should see that log moving whenever you're building
> something via portage.  You *won't* see "distcc gcc" in the make process
> because the distcc FEATURE rewrites the path with /usr/lib/distcc/bin as
> the first item where links for all gcc binaries exist pointing to distcc --
> making it very transparent.  In any case...it is probably better to build
> glibc without distcc; other than that, everything else worked fine for me.
>

You are correct. I just tried it and saw the network activity for distcc. Good 
work Nick.

- -- 
Pat Double, double@×××××××××.com
"In the beginning God created the heaven and the earth."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+X3jkdOmLNuoWoKgRAnaRAJ0ZXS6UkRiqFNVDbFOoX58Fl/KwbQCgqUsj
jjXZY7CZjExrTYB7VExUvR8=
=C3n5
-----END PGP SIGNATURE-----


--
gentoo-dev@g.o mailing list