Summary: | media-video/mplayer fails to configure with CC="ccache gcc" set in environment | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
![]() Here are the top 2 lines :
>>> Configuring source in /var/tmp/portage/media-video/mplayer-1.0_rc2_p20090731/work/mplayer-1.0_rc2_p20090731 ...
Unknown parameter: gcc
*
...
Can't reproduce. Try disabling ccache? (In reply to comment #2) > Try disabling ccache? Nope, same error: >>> Configuring source in /var/tmp/portage/media-video/mplayer-1.0_rc2_p20090731/work/mplayer-1.0_rc2_p20090731 ... Unknown parameter: gcc * There's not much to go on with this information, you have to debug it yourself a bit more. FEATURES="parallel-fetch" within /etc/make.conf wasn't enough, I had to unset CC - which is set to CC="ccache gcc" in my environment. This issue happens only for this particular package for the configure step, other packages / mplayer ebuilds are not affected. You are asking for trouble with such environment variable. For example, some ebuild's set CC to g++ to build C++ code and you would be overriding the CC=$(tc-getCXX) in those. That said, yes, I guess mplayer ebuild could improve too. Oops, didn't mean to close this one :-/ (In reply to comment #6) > You are asking for trouble with such environment variable. Yes, just b/c I did "su" instead of "su -" resulting in having the user env rather than the slightly different env of root. OTOH : "<lu_zero> it's not so nice what the user did but the configurescript should work" :-) (In reply to comment #5) > FEATURES="parallel-fetch" within /etc/make.conf wasn't enough, I had to unset > CC - which is set to CC="ccache gcc" in my environment. This issue happens > only for this particular package for the configure step, other packages / > mplayer ebuilds are not affected. > Why are you putting it manually in CC? Enabling ccache in FEATURES is the correct approach, letting ebuilds that don't support it override it or whatever. (In reply to comment #9) > Why are you putting it manually in CC? Enabling ccache in FEATURES is the > correct approach, letting ebuilds that don't support it override it or > whatever. As already mentioned in comment #8 it was a mistake by myself but even it is uncommon it shouldn't harm emerge, or ? mplayer ebuild quotes cc now, closing |