Arch Linux

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Makechrootpkg: ccache unable to create .ccache dir

After discovering the wonderfully simple chroot tutorial on the wiki for package building I started building all my packages in a chroot. Up till now I could just chroot into the chroot using the makechrootpkg command. However, that recently broke for the Xbmc package somehow (for which I use ccache). The build process complains g++ cannot create executables, then happily quits.

I checked config.log, and there I see this:

## ----------- ##
## Core tests. ##
## ----------- ##

configure:3169: checking for a BSD-compatible install
configure:3237: result: /bin/install -c
configure:3248: checking whether build environment is sane
configure:3298: result: yes
configure:3439: checking for a thread-safe mkdir -p
configure:3478: result: /bin/mkdir -p
configure:3491: checking for gawk
configure:3507: found /bin/gawk
configure:3518: result: gawk
configure:3529: checking whether make sets $(MAKE)
configure:3551: result: yes
configure:3635: checking build system type
configure:3649: result: i686-pc-linux-gnu
configure:3669: checking host system type
configure:3682: result: i686-pc-linux-gnu
configure:4124: checking for g++
configure:4140: found /usr/lib/ccache/bin/g++
configure:4151: result: g++
configure:4178: checking for C++ compiler version
configure:4187: g++ --version >&5
ccache: failed to create //.ccache (Permission denied)
configure:4198: $? = 1
configure:4187: g++ -v >&5
ccache: failed to create //.ccache (Permission denied)
configure:4198: $? = 1
configure:4187: g++ -V >&5
ccache: failed to create //.ccache (Permission denied)
configure:4198: $? = 1
configure:4187: g++ -qversion >&5
ccache: failed to create //.ccache (Permission denied)
configure:4198: $? = 1
configure:4218: checking whether the C++ compiler works
configure:4240: g++ -march=i686 -mtune=generic -O2 -pipe  -Wl,--hash-style=gnu conftest.cpp  >&5
ccache: failed to create //.ccache (Permission denied)
configure:4244: $? = 1
configure:4282: result: no

I am going to create that dir manually, to work around that, but that looks like a bug to me?

Edit: after creating the dir, ./configure finishes successfully. All hunky dory again.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy