Summary: | Setting CC="ccache cc" does not work | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Piechotka <uzytkownik2> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jer |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maciej Piechotka
2009-04-29 06:42:53 UTC
Please attach your /etc/make.conf file and explain how you set up ccache. (In reply to comment #1) > Please attach your /etc/make.conf file and explain how you set up ccache. > CCACHE_SIZE="5G" CFLAGS="-Os -march=pentium4 -pipe -mfpmath=sse -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden" FEATURES="ccache" GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.lagis.at/ http://gentoo.inode.at/" MAKEOPTS="-j2" #SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="acl atm avahi caps cgi cups dbus fastcgi gdbm ipv6 mdnsresponder-compat mmx nat openmp pcre php postgres python sharedmem sse sse2 unicode webdav xattr" Looks, like that was not enough. Add the output of printenv. The problem here is that somewhere you've set CC to "ccache cc" and all of your recent bugs are dupes of this problem. *** Bug 267837 has been marked as a duplicate of this bug. *** *** Bug 267839 has been marked as a duplicate of this bug. *** *** Bug 267840 has been marked as a duplicate of this bug. *** *** Bug 267842 has been marked as a duplicate of this bug. *** Looks like CC is set (incorrectly) in the environment. If you can prove this isn't the case and that perhaps sys-apps/portage is to blame, please provide more information and then reopen this bug report. To explain the Summary change - *most* build systems out there cannot handle a CC variable containing multiple words and will explain exactly as you described in this bug report and its duplicates. *** Bug 267844 has been marked as a duplicate of this bug. *** Yes - you are right - I had set ccache in my .bashrc for my own use. I thought it is a problem with ebuilds (not all of them failed) - so I created several bugs (it was during rebuild so I wasn't surprised very much - only 'normal'). Sorry for trouble. |