Bug 256929

Summary:	media-libs/jasper-1.900.1-r3 hardcodes 'gcc' rather than '$CC'
Product:	Gentoo Linux	Reporter:	Stuart Shelton <srcshelton>
Component:	New packages	Assignee:	Gentoo Science Related Packages <sci>
Status:	RESOLVED WORKSFORME
Severity:	QA	CC:	prefix
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

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!)