On Sun, 28 May 2006 01:54:22 -0230 Jonathan Skanes <[EMAIL PROTECTED]> wrote:
> On May 22, 2006 16:31, Kevin F. Quinn wrote: > > > > If so, do i change the gcc profile on the > > > hardened machines to vanilla before emerging? > > > > That's the only way that will work with distcc. Another option > > would have been to add '-specs=vanilla.specs' to CFLAGS, but distcc > > will reject it (it's a bit tricky to support). > > OK, this being so, can I have the discc init.d script select a > profile and update the environment before running distcc and have it > retain the changes? If so, it should be possible to run a couple > distcc invocations on different ports to support the different > profiles. This would be fabulous as then I can configure the distcc > client to choose the right spec based on distcc port number. Should be simple enough. The only environment thing that matters however is the environment variable GCC_SPECS so you don't need to go switching the system profile all the time. I suggest copying the distccd init.d and conf.d scripts to (say) distccdh. Set the port number in conf.d/distccdh and set GCC_SPECS in init.d/distccdh; probably best to add a line 'export GCC_SPECS="hardened.specs"' before distccd is run. Then just start distccdh. -- Kevin F. Quinn
signature.asc
Description: PGP signature
