Bug 233305 - net-im/farstream-0.2.8 fails to compile with an opencv error
Summary: net-im/farstream-0.2.8 fails to compile with an opencv error
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-18 23:08 UTC by Patrick McMunn
Modified: 2019-08-14 10:45 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick McMunn 2018-11-18 23:08:16 UTC
I'm not sure if this is a problem with farstream or opencv, but farstream compilation hangs with the Farstream-0.2 process hogging nearly 100% CPU at the following point:

g-ir-scanner: link: /bin/sh ../libtool --mode=link --tag=CC cc -o /usr/local/area51/freebsd-ports-kde/net-im/farstream/work/farstream-0.2.8/farstream/tmp-introspectsm6070yi/Farstream-0.2 -export-dynamic -I/usr/local/include -O2 -pipe -march=native -fstack-protector -fno-strict-aliasing /usr/local/area51/freebsd-ports-kde/net-im/farstream/work/farstream-0.2.8/farstream/tmp-introspectsm6070yi/Farstream-0.2.o -L. libfarstream-0.2.la -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lintl -L/usr/local/lib -rpath /usr/local/lib -L/usr/local/lib -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lintl -L/usr/local/lib -fstack-protector
libtool: link: cc -o /usr/local/area51/freebsd-ports-kde/net-im/farstream/work/farstream-0.2.8/farstream/tmp-introspectsm6070yi/.libs/Farstream-0.2 -I/usr/local/include -O2 -pipe -march=native -fstack-protector -fno-strict-aliasing /usr/local/area51/freebsd-ports-kde/net-im/farstream/work/farstream-0.2.8/farstream/tmp-introspectsm6070yi/Farstream-0.2.o -Wl,--export-dynamic -pthread -fstack-protector -Wl,--export-dynamic  -L. ./.libs/libfarstream-0.2.so -L/usr/local/lib -lgio-2.0 -lgthread-2.0 -lgmodule-2.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lintl -pthread -Wl,-rpath -Wl,/usr/local/lib

******************************************************************
* FATAL ERROR:                                                   *
* This OpenCV build doesn't support current CPU/HW configuration *
*                                                                *
* Use OPENCV_DUMP_CONFIG=1 environment variable for details      *
******************************************************************

Required baseline features:
SSE - OK
SSE - OK
SSE2 - OK
SSE2 - OK
SSE3 - OK
SSE3 - OK
POPCNT - NOT AVAILABLE
POPCNT - NOT AVAILABLE
OpenCV(3.4.1) Error: Assertion failed (Missing support for required CPU baseline features. Check OpenCV build configuration and required CPU/HW setup.) in initialize, file /usr/local/area51/freebsd-ports-kde/graphics/opencv-core/work/opencv-3.4.1/modules/core/src/system.cpp, line 487
Comment 1 Patrick McMunn 2018-11-25 17:40:15 UTC
Just as a follow-up, I removed opencv and opencv-core and then reinstalled them from FreeBSD packages instead of from ports. Farstream then compiled and installed successfully. The only thing I can think of that *might* be an issue is using CPUTYPE?=native in make.conf. But this didn't seem to be a problem before, so I don't know why it would suddenly become a problem. In any case, I'll try recompiling opencv from ports without CPUTYPE?=native and see if that resolves the issue.
Comment 2 Patrick McMunn 2018-11-25 21:10:18 UTC
I've confirmed that recompiling graphics/opencv-core after removing CPUTYPE from /etc/make.conf resolves the issue, and farstream now compiles fine. I don't know if this is an issue with OpenCV, Clang 6, or what, but at least it's working now.