mpeg4ip doesn't emerge without alsa-lib even when USE="-alsa" is set.
Error message in /var/tmp/portage/media-video/mpeg4ip-22.214.171.124-r2/temp/autoconf-459.out
***** autoconf *****
configure.in:413: error: possibly undefined macro: AM_PATH_ALSA
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
Seems similar to #177328 and #171942.
Steps to Reproduce:
1. disable alsa in make.conf
2. emerge -uDN world
3. emerge -C alsa-lib alsa-headers
4. emerge mpeg4ip
Failure during eautoreconf.
Failure after eautoreconf or not at all.
Created attachment 129761 [details]
damnit... this is annoying... I have to think of something...
mpeg4ip doesn't ship some of the m4 files containing the macros it uses. This is a common problem I have documented before in the autofailure doc, the solution is to put the missing .m4 files in a tarball and put the extracted directory in AT_M4DIR. What you need is alsa.m4 to fix this bug, but it also misses gtk2's m4 file.
arg, that makes me feel like making the deps not optional... (or p.masking mpeg4ip.. upstream has resigned)
Problem still exists.
Ok, I found somewhere in the internet an alsa.m4 and put it like described into /usr/share/aclocal. Now configure and make were successful.
If it's too much work to edit the ebuild, then maybe it would a good idea to provide alsa.m4 with the autoconf or any other responsible package.
Sorry for the 3rd posting in one day.
But now I did a emerge --sync. And now mpeg4ip wants to reinstall with depencies of alsa-headers and alsa-libs. So it seems that I have to edit the ebuild and put it into my local overlay to avoid installing that alsa-stuff.
Possible solutions for that problem could be:
1. Like written above: Provide alsa.m4 with autoconf package
2. Provide alsa.m4 with the mpeg4ip package
3. Write a warning message into the ebuild that shows up, when the user has not set the alsa useflag.
But please remove that not needed alsa-depency. Thx a lot.
I'm giving up on this package, it is no longer maintained upstream. I will package.mask it in a couple days if no one wants to take it over.
Although the website states that mpeg4ip-1.6.1 tarballs are corrupt, I pulled that version from sourceforge's CVS and placed it on a webserver where I'm the admin of:
I used these tarballs since I've created them and had only one package that failed to compile against this version (but I don't remember which one).
I am unable to maintain this package myself but if anyone else volunteers, feel free to use the tarballs of that webserver.
(In reply to comment #9)
> I'm giving up on this package, it is no longer maintained upstream. I will
> package.mask it in a couple days if no one wants to take it over.
On their website they write:
??? as of 9/28/07, development is stopped, and we are not taking any more contributions.
Ok, the only thing I used from that package is the mp4creator to create an mpeg4-container. Is there an alternative solution? Maybe version 1.6.1 doesn't have these issues.
Olivier: Don't give up. :) Life isn't easy these days.