multimedia/libva fails in configure stage, missing file?

Guido Falsi madpilot at
Sat Jan 3 21:45:37 UTC 2015

On 01/03/15 20:36, Thomas Mueller wrote:
>> It's not used much since most software comes with a precompiled
>> configure script which works fine. automake/autoconf is required only by
>> those ports which come without a precompiled configure script or for
>> some reason require it to be recompiled on FreeBSD.
>>> I have an old 10.0-STABLE installation with no ports/packages built yet, maybe I could try something on that regarding automake and autoconf?
>> You could try but you really shoud investigate why automake dies on your
>> system.

> Now I wonder if automake-1.14.1 would fix the problem.  I guess I'd have to do that port myself, and submit if it seems to work.

You can try, but, since the problem is local to your system, I don't
think updating the software will solve it.

> I checked /usr/local/share/aclocal, found a lot of files with .m4 extension, to the left of .m4 was in most cases a package name.

Mine was just an idea. The cause could be something else. I don't know
much about the automake internals. It simply dies with return code one.
You should try to diagnose that.

> But there was no m4 subdirectory.
> I got the warning message
> aclocal-1.14: warning: couldn't open directory 'm4': No such file or directory
> wonder what that means.

I don't know, but it's just a warning, I don't think it's the cause of
the failure.

I think it is looking for and m4 directory in libva distribution, which
isn't there in fact.

Guido Falsi <madpilot at>

More information about the freebsd-ports mailing list