Date: Mon, 29 Dec 2014 19:40:00 +0100 From: Guido Falsi <madpilot@FreeBSD.org> To: Thomas Mueller <mueller6724@bellsouth.net>, freebsd-ports@freebsd.org Subject: Re: multimedia/libva fails in configure stage, missing file? Message-ID: <54A1A000.7050807@FreeBSD.org> In-Reply-To: <100948.14193.bm@smtp119.sbc.mail.ne1.yahoo.com> References: <251934.51704.bm@smtp118.sbc.mail.ne1.yahoo.com> <54A074AF.4040709@FreeBSD.org> <100948.14193.bm@smtp119.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/29/14 07:09, Thomas Mueller wrote: >> ===> Cleaning for libva-1.4.0 >> ===> License MIT accepted by the user >> ===> Found saved configuration for libva-1.3.1_3 >> ===> libva-1.4.0 depends on file: /usr/local/sbin/pkg - found >> ===> Fetching all distfiles required by libva-1.4.0 for building >> ===> Extracting for libva-1.4.0 >> => SHA256 Checksum OK for libva-1.4.0.tar.bz2. >> ===> Patching for libva-1.4.0 >> ===> Applying FreeBSD patches for libva-1.4.0 >> ===> libva-1.4.0 depends on file: /usr/local/include/linux/videodev2.h - found >> ===> libva-1.4.0 depends on executable: autoconf-2.69 - found >> ===> libva-1.4.0 depends on executable: autoheader-2.69 - found >> ===> libva-1.4.0 depends on executable: autoreconf-2.69 - found >> ===> libva-1.4.0 depends on executable: aclocal-1.14 - found >> ===> libva-1.4.0 depends on executable: automake-1.14 - found >> ===> libva-1.4.0 depends on executable: libtoolize - found >> ===> libva-1.4.0 depends on executable: pkgconf - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/glproto.pc - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/dri2proto.pc - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/pciaccess.pc - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/xext.pc - found >> ===> libva-1.4.0 depends on file: /usr/local/libdata/pkgconfig/xfixes.pc - found >> ===> libva-1.4.0 depends on shared library: libdrm.so - found (/usr/local/lib/libdrm.so.2.4.0) >> ===> libva-1.4.0 depends on shared library: libGL.so - found (/usr/local/lib/libGL.so) >> ===> Configuring for libva-1.4.0 >> aclocal-1.14: warning: couldn't open directory 'm4': No such file or directory >> aclocal-1.14: warning: couldn't open directory 'm4': No such file or directory >> configure.ac:166: installing './compile' >> configure.ac:166: installing './config.guess' >> configure.ac:166: installing './config.sub' >> configure.ac:87: installing './install-sh' >> configure.ac:166: error: required file './ltmain.sh' not found >> configure.ac:87: installing './missing' >> dummy_drv_video/Makefile.am: installing './depcomp' >> automake-1.14: warning: redefinition of 'info' ... >> /usr/local/share/automake-1.14/am/program.am: ... 'info$(EXEEXT)' previously defined here >> test/vainfo/Makefile.am:23: while processing program 'info' >> va/wayland/Makefile.am:33: warning: source file '$(top_srcdir)/va/drm/va_drm_utils.c' is in a subdirectory, >> va/wayland/Makefile.am:33: but option 'subdir-objects' is disabled >> automake-1.14: warning: possible forward-incompatibility. >> automake-1.14: At least a source file is in a subdirectory, but the 'subdir-objects' >> automake-1.14: automake option hasn't been enabled. For now, the corresponding output >> automake-1.14: object file(s) will be placed in the top-level directory. However, >> automake-1.14: this behaviour will change in future Automake versions: they will >> automake-1.14: unconditionally cause object files to be placed in the same subdirectory >> automake-1.14: of the corresponding sources. >> automake-1.14: You are advised to start using 'subdir-objects' option throughout your >> automake-1.14: project, to avoid future incompatibilities. >> autoreconf-2.69: automake failed with exit status: 1 >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/multimedia/libva > > Guido Falsi responded: > >> Hi, A quick test produces similar output here, but those are just >> warnings, here the port goes on and builds successfully. > >> The only error you have id the last line: autoreconf-2.69: automake >> failed with exit status: 1 > >> My suspect is there is some misalignment in the autotools installed on >> your system. Could you try building libva after reinstalling (via >> portmaster is ok) thee automake port? > >> Otherwise I'll check how to get some more output from it and ask you for >> some more tests. > >> Thanks in advance! > > There was > > configure.ac:166 error: required file './ltmain.sh' not found > > Something wrong with the port or configure script? It's strange, but it's not the error that is blocking the build. It's automake which is dieing without reason. > > I looked and found automake and its dependencies (automake-wrapper, autoconf, indexinfo and perl5.20) all up-to-date, so nothing there to upgrade. > > Or should I portmaster -f anyway? > Yes, please try that. Maybe something got confused in one of those ports. -- Guido Falsi <madpilot@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54A1A000.7050807>