Date: Sun, 28 Dec 2014 07:59:26 +0000 (UTC) From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-ports@freebsd.org Cc: madpilot@freebsd.org Subject: multimedia/libva fails in configure stage, missing file? Message-ID: <251934.51704.bm@smtp118.sbc.mail.ne1.yahoo.com>
next in thread | raw e-mail | index | archive | help
I followed the instructions in UPDATING for updating graphics/png, and am snagged on multimedia/libva as a dependency of www/seamonkey and multimedia/ffmpeg. Now I am left without Seamonkey, which was removed in the upgrade process, but subsequently managed to build www/qupzilla. ===>>> www/seamonkey 1/12 >> alsa-plugins-1.0.27_2 >> ffmpeg-2.2.4_1,1 >> multimedia/libva (3/63) ESC]0;portmaster: www/seamonkey 1/12 >> alsa-plugins-1.0.27_2 >> ffmpeg-2.2.4_1,1 >> multimedia/libva (3/63)^G ===> 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 *** Error code 1 Did I do something wrong, or is that a known problem? Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?251934.51704.bm>