ionic at macports.org
Fri Aug 21 08:58:47 PDT 2015
I would appreciate you taking a look at that thing.
Since boost was updated, libvisio-0.1 fails to build for me (you probably
upgraded libvisio-0.1 on your system prior to the boost update, so got out free.)
I don't know what causes the problem exactly, but libvisio-0.1 never intended to
link boost libraries - only use its header files.
Something keeps pulling in boost::system::system_category() if
BOOST_SYSTEM_NO_DEPRECATED is not defined and requires linking to libboost_system.
Actually linking to libboost_system would require changes to the autotools
files, as there's no library check etc.
Defining BOOST_SYSTEM_NO_DEPRECATED works, but is probably merely a workaround
and could break with the next boost update (if libvisio-0.1 uses newly
deprecated macros/functions or something along these lines.)
(Commit log for reference only)
Author: ionic at macports.org
Date: 2015-08-21 08:50:04 -0700 (Fri, 21 Aug 2015)
libvisio-0.1: workaround for boost 1.59.0 pulling in
boost::system::system_category() from libboost_system. Delete as soon as fixed.
--- trunk/dports/graphics/libvisio-0.1/Portfile 2015-08-21 13:19:10 UTC (rev 139613)
+++ trunk/dports/graphics/libvisio-0.1/Portfile 2015-08-21 15:50:04 UTC (rev 139614)
@@ -46,6 +46,12 @@
+# Needed for current boost? Libvisio doesn't want to link boost libraries, only
use its headers.
+# Something pulls in boost::system::system_category(), though, which requires
+# as of boost 1.59.0.
+# This should be deleted ASAP.
# delete binaries that conflict with libvisio
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 884 bytes
Desc: OpenPGP digital signature
More information about the macports-dev