Summary: | Transcode-0.6.11 is broken by FEATURE="confcache" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alec Warner <antarus> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dev-portage |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Moves the CFLAGS change to a seperate line |
Description
Alec Warner (RETIRED)
2005-03-06 20:09:00 UTC
It appears that this line in the ebuild is naughty. econf doesn't like changing CFLAGS on the command line. old code: # econf ${myconf} CFLAGS="${CFLAGS} -DDCT_YUV_PRECISION=1" || die My test: econf ${myconf} CFLAGS="${CFLAGS} -Wall" || die both hork the build process. Just specifying: econf ${myconf} ${CFLAGS} || die makes the build go fine. Learning as I go here. econf doesn't take any parameters save configure options. Move the CFLAGS line to above the econf line; then call econf ${myconf} and you should get the behavior you want with no h0rkage. Also noting that changing CFLAGS during that stage appears to break CFLAGS tracking. Created attachment 52825 [details, diff]
Moves the CFLAGS change to a seperate line
econf doesn't take CFLAGS as arguements, only configure options.
the right fix is in transcode-0.6.14.ebuild: inherit ... flag-o-matic ... append-flags -DDCT_YUV_PRECISION=1 ... Thanks for reporting, append-flags now is used by transcode-0.6.11 |