CC is clang:
% CC --version
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.3
Thread model: posix
Of course, this is even more interesting:
% cat /usr/bin/CC
#!/bin/sh
# $FreeBSD: stable/10/usr.bin/clang/clang/CC.sh 293782 2016-01-12 19:33:43Z
dim $
# This file is in the public domain.
exec /usr/bin/c++ "$@"
Adding -lstdc++ or -lc++ (seems that that's the clang standard c++ library)
after the last .so file doesn't link. Neither does using clang++.
Looking over the 0.3.0 port (which builds), I note that it uses c++, not
CC. Should be the same. It is also flagged as using gmake, though I'm not
sure that makes a difference.
Here's the last bit of the 0.3.0 link:
-L/usr/local/lib /usr/local/lib/libboost_filesystem.so
/usr/local/lib/libboost_system.so /usr/local/lib/libboost_thread.so
-pthread /usr/local/lib/qt4/libQtGui.so /usr/local/lib/qt4/libQtCore.so
-lsigrok -lglib-2.0 -lintl -lsigrokdecode
-Wl,-rpath,/usr/local/lib:/usr/local/lib/qt4:
And for comparison, here's the failing 0.4.0 build:
-L/usr/local/lib /usr/local/lib/libboost_filesystem.so
/usr/local/lib/libboost_system.so /usr/local/lib/libboost_thread.so
/usr/local/lib/libboost_unit_test_framework.so
/usr/local/lib/libQt5Svg.so.5.5.1 -lpthread -lsigrokcxx -lsigrok
-lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lsigrokdecode -lglib-2.0 -lintl
/usr/local/lib/libQt5Widgets.so.5.5.1 /usr/local/lib/libQt5Gui.so.5.5.1
/usr/local/lib/libQt5Core.so.5.5.1 -Wl,-rpath,/usr/local/lib:
-Wl,-rpath-link,/usr/local/lib
The only really significant difference I see is using -lpthread instead of
-pthread, but that doesn't work either. the Qt lib directory isn't
searched, but Qt5 doesn't appear to have one. Order, maybe?
On Tue, Jul 12, 2016 at 10:34 AM Peter Stuge <pe...@stuge.se> wrote:
> Mike Meyer wrote:
> > /usr/bin/CC -fPIC -O2 -g -DNDEBUG
> CMakeFiles/pulseview.dir/main.cpp.o
> ..
> > CMakeFiles/pulseview.dir/qrc_pulseview.cpp.o -o pulseview
> > -L/usr/local/lib /usr/local/lib/libboost_filesystem.so
> > /usr/local/lib/libboost_system.so /usr/local/lib/libboost_thread.so
> > /usr/local/lib/libboost_unit_test_framework.so
> > /usr/local/lib/libQt5Svg.so.5.5.1 -lpthread -lsigrokcxx -lsigrok
> > -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lsigrokdecode -lglib-2.0 -lintl
> > /usr/local/lib/libQt5Widgets.so.5.5.1 /usr/local/lib/libQt5Gui.so.5.5.1
> > /usr/local/lib/libQt5Core.so.5.5.1 -Wl,-rpath,/usr/local/lib:
> > -Wl,-rpath-link,/usr/local/lib
>
> Does the FreeBSD CC deal with C++ code and object files?
>
> What if you run that command by hand, with clang++ instead of /usr/bin/CC ?
>
>
> //Peter
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> sigrok-devel mailing list
> sigrok-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sigrok-devel
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
