opencv update

[Daniel Nebdal]

On Wed, Dec 4, 2013 at 2:10 PM, Ajtim <lumiwa at gmail.com> wrote:

> 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
>
> If you think configure made a mistake, make sure you are using the latest
> version from Git.  If the latest version fails, report the problem to the
> ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
> Include the log file "config.log" produced by configure as this will help
> solving the problem.
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to wg at FreeBSD.org [maintainer] and attach the
> "/usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/config.err" including the
> output of the failure of your make command. Also, it might be a good idea
> to
> provide an overview of all packages installed on your system (e.g. a
> /usr/local/sbin/pkg-static info -g -Ea).
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/multimedia/ffmpeg0
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/multimedia/ffmpeg0
>
> ===>>> make failed for multimedia/ffmpeg0
> ===>>> Aborting update
>
> ===>>> Update for multimedia/ffmpeg0 failed
> ===>>> Aborting update
>
> ===>>> Killing background jobs
> Terminated
> ===>>> The following actions were performed:
>         Installation of graphics/opencv-core (opencv-core-2.4.7)
>         Upgrade of ffmpeg-2.1.1,1 to ffmpeg-2.1.1_1,1
>
>
> ===>>> You can restart from the point of failure with this command line:
>        portmaster <flags> multimedia/ffmpeg0
> graphics/gstreamer-plugins-opencv graphics/opencv graphics/openimageio
> x11/xterm
>
> Thank you.
> --
> Mitja
> -------
> http://www.redbubble.com/people/lumiwa



I ran into something like that when the relevant files were installed, but
didn't work (missing symbols in something it was linked to, I believe).
What does the config.err file say?

-- 
Daniel Nebdal