[asio] Massive regression failures
I am running the regression tests on the develop branch with Oracle Solaris Studio12.4 on Solaris 11.2 OS. Tests for asio fail as follows: ../boost/system/config.hpp", line 34: Error: #error Must not define both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK. I looked at the developer issues on http://www.boost.org/development/tests/develop/developer/issues.html and see that asio tests fail similarly. I'm not sure what causes both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK. to be defined on the command line. Any idea on how this can be fixed? Thanks, Aparna
On Thu, Mar 5, 2015 at 12:55 PM, Aparna Kumta
I am running the regression tests on the develop branch with Oracle Solaris Studio12.4 on Solaris 11.2 OS.
Tests for asio fail as follows: ../boost/system/config.hpp", line 34: Error: #error Must not define both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK.
I looked at the developer issues on http://www.boost.org/development/tests/develop/developer/issues.html
and see that asio tests fail similarly.
I'm not sure what causes both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK. to be defined on the command line.
Any idea on how this can be fixed?
The same symptom came up in the Boost.Test library in [test] Fix Boost.Build issues (#29) The relevant commit is https://github.com/boostorg/test/commit/e2fd5e847b568c859c91a9bc56f14ef66a99... According to Jürgen Hunold comment: "I've removed the explicit linking to Boost.System and Boost.Timer as both dependencies are handled by Boost.Build automagically. The test basic_cstring_test [ test-btl-lib run : basic_cstring_test : boost_unit_test_framework/static ] requires static runtime. Unconditionally adding both libraries globally (for all tests) results in linking against both shared and static library. And you only need instead of to draw header dependencies." His comment is specific to Boost.Test, but if you look at the changes made by his commit (see link above) you can see the fix, which is very simple. I think Boost.Thread got bitten by a similar problem. HTH, --Beman
On 03/06/15 13:31, Beman Dawes wrote:
On Thu, Mar 5, 2015 at 12:55 PM, Aparna Kumta
wrote: I am running the regression tests on the develop branch with Oracle Solaris Studio12.4 on Solaris 11.2 OS.
Tests for asio fail as follows: ../boost/system/config.hpp", line 34: Error: #error Must not define both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK.
I looked at the developer issues on http://www.boost.org/development/tests/develop/developer/issues.html
and see that asio tests fail similarly.
I'm not sure what causes both BOOST_SYSTEM_DYN_LINK and BOOST_SYSTEM_STATIC_LINK. to be defined on the command line.
Any idea on how this can be fixed? The same symptom came up in the Boost.Test library in [test] Fix Boost.Build issues (#29)
The relevant commit is https://github.com/boostorg/test/commit/e2fd5e847b568c859c91a9bc56f14ef66a99...
According to Jürgen Hunold comment:
"I've removed the explicit linking to Boost.System and Boost.Timer as both dependencies are handled by Boost.Build automagically. The test basic_cstring_test [ test-btl-lib run : basic_cstring_test : boost_unit_test_framework/static ] requires static runtime. Unconditionally adding both libraries globally (for all tests) results in linking against both shared and static library. And you only need instead of to draw header dependencies."
His comment is specific to Boost.Test, but if you look at the changes made by his commit (see link above) you can see the fix, which is very simple. I think Boost.Thread got bitten by a similar problem. Thanks. I will give it a try.
Aparna
HTH,
--Beman
_______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (2)
-
Aparna Kumta
-
Beman Dawes