Tags Tags

Bug#672570: ccache: Does not handle nonwriteable/not-a-directory HOME gracefully, breaks autogen

May 12th, 2012 - 03:30 am ET by Andreas Metzler | Report spam
Help Create a new topic
Package: ccache
Version: 3.1.7-1
Severity: normal

Hello,

it is not possible to build GNU autogen with ccache installed and in
PATH. Afaict this caused by autogen setting HOME=/dev/null.
|
| ccache: failed to create /dev/null/.ccache (Not a directory)
|

ccache should be able to handle this more gracefully and not try to write to
nonwriteable/not-a-directory HOME.

The fact that it tries to to so even with CCACHE_DISABLE=true is
broken, isn't it?
(SID)ametzler@argenau:/tmp/AUTOGEN/autogen-5.15$ env HOME=/dev/null CCACHE_DISABLE=true gcc -Wall -o hello hello.c
ccache: failed to create /dev/null/.ccache (Not a directory)

thanks, cu andreas

Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ccache depends on:
ii libc6 2.13-32
ii zlib1g 1:1.2.6.dfsg-2

ccache recommends no packages.

Versions of packages ccache suggests:
pn distcc <none>





To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Similar topics

Display all similar topics

Replies

#1 Joel Rosdahl
May 13th, 2012 - 03:00 pm ET | Report spam

Hi,

On 12 May 2012 09:22, Andreas Metzler wrote:
it is not possible to build GNU autogen with ccache installed and in
PATH. Afaict this caused by autogen setting HOME=/dev/null.
[...]
ccache should be able to handle this more gracefully and not try to write


to
nonwriteable/not-a-directory HOME.



This was actually brought this up on the ccache mailing list recently:
http://www.mail-archive.com//msg00754.html. I still
think that not failing silently is a good thing in general, but having a
special exception for HOME=/dev/null could perhaps be a good idea. On the
other hand, if ccache disables itself when HOME=/dev/null (and when
CCACHE_DIR isn't set explicitly), you won't get the chance to know that you
need to set CCACHE_DIR to use ccache when compiling autogen...

The fact that it tries to to so even with CCACHE_DISABLE=true is
broken, isn't it?



Yes, that's a bug. It will be fixed in ccache 3.2.



Hi,<br><br>On 12 May 2012 09:22, Andreas Metzler &lt;<a href="mailto:"></a>&gt; wrote:<br>&gt; <span style>it is not possible to build GNU autogen with ccache installed and in</span><div>
<span style>&gt; PATH. Afaict this caused by autogen setting HOME=/dev/null.</span><br><div>&gt; [...]<br><div>&gt; ccache should be able to handle this more gracefully and not try to write to<br>&gt; nonwriteable/not-a-directory HOME.<br>
<br><div>This was actually brought this up on the ccache mailing list recently: <a href="http://www.mail-archive.com//msg007...t;>http://www.mail-archive.com//msg00754.html</a>. I still think that not failing silently is a good thing in general, but having a special exception for HOME=/dev/null could perhaps be a good idea. On the other hand, if ccache disables itself when HOME=/dev/null (and when CCACHE_DIR isn&#39;t set explicitly), you won&#39;t get the chance to know that you need to set CCACHE_DIR to use ccache when compiling autogen...</div>
<div><br></div><div>&gt; The fact that it tries to to so even with CCACHE_DISABLE=true is<br>&gt; broken, isn&#39;t it?<br><br></div><div>Yes, that&#39;s a bug. It will be fixed in ccache 3.2.</div><div><br></div><div>-- Joel</div>
</div></div></div>




To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search