Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 256929 - media-libs/jasper-1.900.1-r3 hardcodes 'gcc' rather than '$CC'
Summary: media-libs/jasper-1.900.1-r3 hardcodes 'gcc' rather than '$CC'
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High QA (vote)
Assignee: Gentoo Science Related Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-30 12:45 UTC by Stuart Shelton
Modified: 2010-07-02 20:46 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Shelton 2009-01-30 12:45:54 UTC
During jasper's build, there are many instances of:

../../../libtool: line 96: gcc: command not found
../../../libtool: line 97: gcc: command not found
/opt/gentoo/usr/bin/sed: -e expression #1, char 0: no previous regular expression
/opt/gentoo/usr/bin/sed: -e expression #1, char 0: no previous regular expression
/opt/gentoo/usr/bin/sed: -e expression #1, char 0: no previous regular expression
/opt/gentoo/usr/bin/sed: -e expression #1, char 0: no previous regular expression

... followed by:


 * QA Notice: command not found:
 * 
 *      ../../../libtool: line 96: gcc: command not found
 *      ../../../libtool: line 97: gcc: command not found
 *      ../../libtool: line 96: gcc: command not found
 *      ../../libtool: line 97: gcc: command not found

(all repeated multiple times)

Having said this, the package does seem to complete its build successfully.
Comment 1 Justin Lecher (RETIRED) gentoo-dev 2010-06-24 12:56:55 UTC
Works here, assumed to be fixed. In any case of objections race hands!
Comment 2 Stuart Shelton 2010-07-02 20:46:42 UTC
Ah, it looks as if I may have mis-filed this bug: it was actually intended to be a Prefix bug which occurs when building on IRIX... or, at least, it was a year and a half ago :o

I'll post a new bug...

(Unless you did test on a platform which lacks gcc, and so this really *is* fixed!)