| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
I am using portage-2.0.47-r7 and the latest distcc in ~x86 and it still does |
| 5 |
not work. Are there specific ebuilds that disable distcc? I tried updating |
| 6 |
distcc, ccache and parted as tests. No distcc prepended to gcc. |
| 7 |
|
| 8 |
On Friday 28 February 2003 01:51 am, Nick Jones wrote: |
| 9 |
> > Seems like the distcc feature stopped working since I upgraded to the |
| 10 |
> > latest portage. Can anyone confirm? |
| 11 |
> > |
| 12 |
> > gcc is being called directly from the installed path instead of the |
| 13 |
> > wrapper directory generated by distcc. it looks like portage isn't |
| 14 |
> > setting the PATH to include /usr/lib/distcc/bin as the first item. This |
| 15 |
> > worked fine in portage-2.0.47-r3 but not -r5 or -r6. |
| 16 |
> |
| 17 |
> use >=portage-2.0.47-r7 |
| 18 |
> |
| 19 |
> -- |
| 20 |
> gentoo-dev@g.o mailing list |
| 21 |
|
| 22 |
- -- |
| 23 |
Pat Double, double@×××××××××.com |
| 24 |
"In the beginning God created the heaven and the earth." |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 27 |
|
| 28 |
iD8DBQE+X0hMdOmLNuoWoKgRArh3AJ43NYzP4LF01SFzkjS2oNxieeDDPwCcDtf6 |
| 29 |
koy4XIkE0FsHUwiUdH4TTHU= |
| 30 |
=6HR7 |
| 31 |
-----END PGP SIGNATURE----- |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives