Bug 54658 – portage-2.0.51_pre11 broke ccache support

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Brian Harring (RETIRED) 2004-06-21 09:00:03 UTC]

I haven't yet pinned down exactly what is the cause of this, but 
FEATURES="ccache" emerge portage bails w/ a gcc compilation failure- the problem is that it's attempting to access /var/tmp/portage/home/.ccache (which doesn't exist).  You end up with errors similar to this-
Checking libc version... ccache: failed to create /var/tmp/portage/homedir/.ccache (No such file or directory)

ldd: ./libctest: No such file or directory

rm: cannot remove `libctest': No such file or directory

gcc -march=i386 -O1 -pipe  -D_GNU_SOURCE -DPIC -fPIC -D_REENTRANT -Wall -c libsandbox.c
ccache: failed to create /var/tmp/portage/homedir/.ccache (No such file or directory)
make: *** [libsandbox.o] Error 1


This affects both running as root and sudo'ing.  So far, I know the portage ebuild is affected, as is net-mail/fetchmail.  I'd expect it to  affect all packages, but haven't had the time to fully test it yet.


emerge info.
Portage 2.0.51-cvs (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6)
=================================================================
System uname: 2.6.6 i686 AMD Athlon(tm) XP 2100+
Gentoo Base System version 1.4.3.13
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
Binutils: sys-devel/binutils-2.14.90.0.7-r4
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=athlon-xp -O2 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-mcpu=athlon-xp -O2 -pipe"
DISTDIR="/usr/gentoo-files/distfiles"
FEATURES="autoaddcvs buildpkg ccache cvs notitles sandbox"
GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/gentoo-files/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/gentoo-cvs/gentoo-x86"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb crypt cups doc encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 guile imlib informix innodb java jpeg libg++ libwww motif mozilla moznocompose moznoirc moznomail mpeg mysql nas ncurses nls offensive oggvorbis opengl pam pdflib perl php png postgres python qt quicktime readline ruby samba sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xml xml2 xmms xv xvid zlib"

[Comment 1 Brian Harring (RETIRED) 2004-06-21 09:33:14 UTC]

Bug is caused by the addition of a default HOME export in environ (line 1834 of portage.py roughly)- if HOME isn't set (which across all my users and root it isn't), portage decided /var/tmp/portage/homedir will do, and ccache borks due to /var/tmp/portage/homedir/.ccache/ not existing.

So, either create the directories, or nuke the setting of HOME to a default location when it's unset.  I lean towards the later personally, since exempting kde ebuilds, no ebuild should be screwing w/ files in $HOME- the kde ebuilds are covered via their own HOME hacks.

What does exporting the home var address/fix?  Strikes me as cruft... course I have a major dislike of any ebuild thinking it should be installing things into HOME, since unless the app is smart enough to recreate it's additions to home on the fly, the additions to home are limited to a single user...

[Comment 2 Brian Harring (RETIRED) 2004-07-29 17:37:19 UTC]

pre13 is out, closing.