Date: Mon, 5 Jan 2015 04:37:20 +0000 (UTC) From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-ports@freebsd.org Cc: madpilot@freebsd.org Subject: Re: multimedia/libva fails in configure stage, missing file? Message-ID: <841102.2852.bm@smtp113.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> <54A1A000.7050807@FreeBSD.org> <92121.6371.bm@smtp115.sbc.mail.ne1.yahoo.com> <54A32410.9020300@FreeBSD.org> <106917.74102.bm@smtp112.sbc.mail.ne1.yahoo.com> <54A6DB7A.5000905@FreeBSD.org> <987407.23877.bm@smtp120.sbc.mail.ne1.yahoo.com> <54A862E2.2070102@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
from Guido Falsi: > 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. I don't know how to diagnose automake's failing, except to try on another FreeBSD, NetBSD or Linux system. I see some ports that previously didn't list automake or autoconf as dependency now do, such as mutt. It also looks like, if I have a useful system, I really should back it up, the whole OS + packages/ports, to another partition. That would protect not only against a massive portupgrade/portmaster removing and failing to rebuild a port but also against messing the base system with an update that turns out to be buggy. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?841102.2852.bm>