On Thu, Dec 5, 2013 at 12:07 AM, Lowell Gilbert < freebsd-ports-lo...@be-well.ilk.org> wrote:
> Lowell Gilbert <freebsd-ports-lo...@be-well.ilk.org> writes: > > > Ajtim <lum...@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. > > I didn't verified it yet, but my assumption that it's combination of wrong order of linker parameters and --as-needed option. Libraries placed before object file, which uses them (wrong order), so at the time of theirs occurrence they are unneeded and therefore skipped. Similar problem would to occur independently of --as-needed if static libraries would be used instead of dynamic, or linker occur more strict/conservative. PS. @Mark: cvCreateImageHeader, symbol, which test program tries to find in opencv-core.so library, exists there and exported indeed. It absent in the output of plain nm (or 'nm -a' in your case) just because library is heavy stripped (removed anything unneeded for ld.so). If use 'nm -D', you will see that symbol. -- Andrew W. Nosenko <andrew.w.nose...@gmail.com> _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
