Date: Wed, 04 Dec 2013 17:07:51 -0500 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: freebsd-ports@freebsd.org Cc: Ajtim <lumiwa@gmail.com>, wg@freebsd.org Subject: Re: opencv update Message-ID: <448uw0fex4.fsf@lowell-desk.lan> In-Reply-To: <44iov4fl19.fsf@lowell-desk.lan> (Lowell Gilbert's message of "Wed, 04 Dec 2013 14:55:46 -0500") References: <9791025.9uybD67rLo@lumiwa.farms.net> <44iov4fl19.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> writes: > Ajtim <lumiwa@gmail.com> writes: > >> I did what is in /usr/ports/UPDATING and looks like I am in trouble >> now. My system is FreeBSD 10.0-BETA4 (amd64): >> >> ===> FreeBSD 10 autotools fix applied to >> /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure >> ERROR: opencv-core not found > > Looks like ffmpeg0's opencv support should now depend on graphics/opencv > rather than graphics/opencv-core. I'm testing this theory now... No, that's not right. There's some configure-script editing in the port that I hadn't noticed. It's probably a minor fix, but in the meantime turning off ffmpeg0's option for opencv should get you around it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448uw0fex4.fsf>