| 1 |
This has been fixed in the newer releases of distcc (1.0 and above) by |
| 2 |
calling gcc-config --get-bin-path. 1.0 and 1.1 are both in ~x86 due to |
| 3 |
the stable portage freeze, but work fine. |
| 4 |
|
| 5 |
On Sat, 2003-02-08 at 04:46, MAL wrote: |
| 6 |
> This is a solved problem, but I thought i'd share it with you. |
| 7 |
> |
| 8 |
> On my machine at least, distccd, (which was running as nobody), wasn't |
| 9 |
> getting the path to gcc, (as provided by sourcing /etc/profile.env). |
| 10 |
> |
| 11 |
> This was resulting in remote compiles failing with: 'gcc: command not |
| 12 |
> found'. |
| 13 |
> |
| 14 |
> This happens because distcc isn't being run in a login shell by |
| 15 |
> start-stop-daemon, and so /etc/profule isn't sourced, (as it is when you |
| 16 |
> login). On a side note, suing to root, didn't give me gcc either... I |
| 17 |
> had to add '. /etc/profile' to my root's .bashrc. |
| 18 |
> |
| 19 |
> Anyway, to fix this I simply added '. /etc/profile' to |
| 20 |
> /etc/init.d/distccd, just before it starts distccd. |
| 21 |
> |
| 22 |
> These dynamically pathed gcc's have caused me so many problems :/ |
| 23 |
> |
| 24 |
> MAL |
| 25 |
> |
| 26 |
> |
| 27 |
> -- |
| 28 |
> gentoo-dev@g.o mailing list |
| 29 |
-- |
| 30 |
--Eric Andresen |
| 31 |
ndiin@×××.edu |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives