Bug 15616 – emerge bzip2 failed if FEATURES=..distcc..

• Product: Portage Development
• Status: RESOLVED WORKSFORME

[Description Michael Tartsch 2003-02-13 04:29:20 UTC]

> emerge bzip2
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/bzip2-1.0.2-r2 to /
>>> md5 ;-) bzip2-1.0.2.tar.gz
>>> Unpacking source...
>>> Unpacking bzip2-1.0.2.tar.gz
>>> Source unpacked.
make: *** No rule to make target `gcc'.  Stop.

!!! ERROR: sys-apps/bzip2-1.0.2-r2 failed.
!!! Function src_compile, Line 39, Exitcode 2
!!! (no error message)
----------------------------
> make.conf
..
MAKEOPTS="-j4"
DISTCC_HOSTS="localhost ...
...
FEATURES="digest ccache sandbox distcc"
------------------------
> /usr/portage/sys-apps/bzip2/bzip2-1.0.2-r2.ebuild
line 34
        myconf="CC=${CC:-gcc}"
probably not compatible with portage distcc

why does this ebuild has this special CC handling?


Reproducible: Always
Steps to Reproduce:

1. add distcc to FEATURES in make.conf
2. emerge bzip2
3.

Actual Results:  
make: *** No rule to make target `gcc'.  Stop.


Expected Results:  
:-)

[Comment 1 Alastair Tse (RETIRED) 2003-02-13 09:47:53 UTC]

zwelch,

just a suggestion, maybe instead of prefixing distcc to the CC variable, we should have an alias is similar to:

alias distcc-gcc="distcc gcc"
alias distcc-g++="distcc g++"

and then use CC="distcc-gcc" and CXX="distcc-g++"

This would solve alot of problems with quoting MAKEOPTS etc. although i haven't thought hard about any side effects.

[Comment 2 Zach Welch (RETIRED) 2003-02-13 13:51:01 UTC]

First, you are using a very old bzip2 ebuild.  Second, I would guess that
you are not using the latest distcc ebuild.  Please do an emerge rsync
and try first emerging the new distcc followed by bzip2.

Also, the new integrated C wrapper support provided by bug 13897 works better 
than the aliasing suggested in commnet #1.