Summary: | media-libs/libmp4v2-1.5.0.1-r2 won't compile: Failed running autoconf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gregg Casillo <gregg.casillo> |
Component: | [OLD] Library | Assignee: | Olivier Crete (RETIRED) <tester> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugzilla, flameeyes, optiluca, prefix |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-t-766292.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
autoconf.out
build.log emerge --info |
Description
Gregg Casillo
2009-05-24 05:49:26 UTC
Taking the clue from the autoconf.out error, I decided to try installing gtk+-2.16.1 to see if that might satisfy libmp4v2. Sure enough, libmp4v2-1.5.0.1-r2 compiled successfully and emerged. If someone can make gtk+ a dependency for the libmp4v2 ebuild, I think this will resolve the problem. I can only assume AT_NO_RECURSIVE="yes" in the ebuild isn't working, and now it requires >=x11-libs/gtk+-2 to compile for correct aclocal macro. It's possible to change the AM_PATH_GTK_2_0 to a pkg-config call, this was you won't need the depend and can only add dev-util/pkgconfig to buildtime deps. I've done this in e.g. gentoo-x86/media-video/xvattr/files/xvattr-1.3-gtk.patch That should not be a dependence... Why now? Maybe a gtk flag must be needed... im not going to install gtk+ Give me a few minutes and I'll get to it, easy way out: just remove the call, we don't give a damn about gtk+ in that package :p 28 May 2009; Diego E. Pettenò (flameeyes) libmp4v2-1.5.0.1-r2.ebuild: Don't try to look for the glib/gtk autoconf macros, not needed and causes additional deps. I guess this is fixed, reopen if not. I've synced just now (with several different servers) and the problem still exists. Given that it was 7 hours ago this bug was closed I think the fix Diego made should've reached out by now. The error message is the same as before. Reopen? I'll restate that this is not fixed yet. I'll attatch my emerge --info and the buildlog, but it's basically the same. Steps to reproduce: 1. Emerge libmp4v2 2. Autoconf fails Created attachment 192829 [details]
autoconf.out
Created attachment 192830 [details]
build.log
Created attachment 192831 [details]
emerge --info
suggested solution, get rid of the libmp4v2 package and use the version in faad2, sine libmp4v2 is sadly no longer maintained upstream... A few packages do depend on this still, until they can support something else... but I did fix this properly, I got the sed wrong the first time around (I didn't close the bug on purpose because I wasn't entirely sure I was awake enough when I did commit the first). I think those packages can be built against faad2 too It still fails for me too. Same error so I won't paste redundant logs unless asked to. The ebuild's revision where this should be fixed is 1.3 (head -n3 of the ebuild file). In my case it is mplayer that's depending on this library, I'm not 100% sure since I'm not at the computer in question but a not too far fetched guess would be the mp4 USE-flag. This is for a headless server, thus emerging GTK+ is not really an option since that'd pull several x11 libraries too. I'll check this when I get home tomorrow but the sed line looks right now. Thanks a lot Diego! |