Thanks for diagnosing the problem here; I too would like too see this fixed and I apologize if my first response is too terse.
On 20 April 2011 11:02, Dominique Brazziel <[email protected]> wrote: > "I really think hardcoding ccache to run /usr/bin/cc is a bad idea and > Debian should not take this patch." > > This patch doesn't hardcode ccache, it tells distccd to run > '/usr/bin/cc'. That was a typo. Of course I meant 'distcc'. > "Instead, either run with a useful > $HOME," > Well, distccd is the component that doesn't have a sensible $HOME, > (it runs with HOME='/' as stated above). That's true, but it can be changed. It seems to me the first thing is to determine what we want to have happen when ccache is run by distcc. If we want distccd to be able to cache things, then it needs to have a home directory, I guess somewhere under /var/cache, or perhaps just to get a ccache directory in eg /var/cache/distcc-ccache. On the other hand if distccd is really going to have no home directory of its own, then ccache should not complain when it's unable to write to /.ccache. On the whole I think this is my favourite solution: propose a ccache patch that just silently does nothing if HOME==/. Lots of people reconfigure ccache and distcc to run non-standard compilers for various reasons such as embedded or cross development. Hardcoding the path, especially doing so silently, will cause confusion for them and I don't think it is addressing the essential problem there. Martin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
