Summary: | SexyPSF 0.4.7 doesn't compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Masover <ninja> |
Component: | Current packages | Assignee: | Harald van Dijk (RETIRED) <truedfx> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to sexypsf-0.4.7.ebuild |
Description
David Masover
2006-01-16 15:42:30 UTC
Created attachment 77302 [details, diff]
Patch to sexypsf-0.4.7.ebuild
Builds the commandline app after the plugin, instead of the other way around. Makes sexypsf actually compile for me, on my amd64.
Thanks for the patch, but it's a workaround, and not a fix, because it then uses the object files built with -fPIC to generate the application (only the library should be built with -fPIC). I can build it just fine here, so I'm not really sure this is the problem, but could you please instead try changing (in the original ebuild, of course) emake CPU="${CPU}" XMMSCONF="${XMMSCONF}" clean sexypsf || die "emake failed" to make clean || die "make clean failed" emake CPU="${CPU}" XMMSCONF="${XMMSCONF}" sexypsf || die "emake failed" (moving the 'clean' to a separate 'make' invocation) and report back whether that fixes it? If it doesn't fix it, could you please provide your emerge --info, and the full output of `emerge sexypsf` ? Please re-open when you get the chance to test. Harald, I get the same error as David with the original ebuild (I think it is related to the xmms or bmp plugin, it compiles without them), so I tested your fix and it works, you can commit it. Cheers Thanks, and done. |