-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[boost-thread] build failure with VCPKG_BUILD_TYPE release #8613
Comments
Related to #7559 |
This also fails on debian:buster, which uses gcc 8.3.0. |
Can somebody try this workaround ? diff --git a/ports/boost-modular-build-helper/Jamroot.jam b/ports/boost-modular-build-helper/Jamroot.jam
index b39bdc493..5874957d0 100644
--- a/ports/boost-modular-build-helper/Jamroot.jam
+++ b/ports/boost-modular-build-helper/Jamroot.jam
@@ -67,7 +67,7 @@ if "@PORT@" != "boost-date-time"
use-project /boost/date_time : . ;
lib boost_date_time : : <file>"@CURRENT_INSTALLED_DIR@/lib/@BOOST_LIB_PREFIX@boost_date_time@BOOST_LIB_RELEASE_SUFFIX@" <variant>release -<library>/boost/date_time//boost_date_time ;
- lib boost_date_time : : <file>"@CURRENT_INSTALLED_DIR@/debug/lib/@BOOST_LIB_PREFIX@boost_date_time@BOOST_LIB_DEBUG_SUFFIX@" <variant>debug -<library>/boost/date_time//boost_date_time ;
+# lib boost_date_time : : <file>"@CURRENT_INSTALLED_DIR@/debug/lib/@BOOST_LIB_PREFIX@boost_date_time@BOOST_LIB_DEBUG_SUFFIX@" <variant>debug -<library>/boost/date_time//boost_date_time ;^M
explicit boost_date_time ;
} |
Ya, removing that line works for me. |
I rebased the commits from #9224 on top of current vcpkg master and can confirm that those changes fix the problem on Windows 10 as well as an Debian Buster. |
The PR has been merged, pleasse get latest source and try agin. |
@PhoebeHui works fine now, thanks! |
@PhoebeHui It works fine. Great. Thank you. |
Host Environment
To Reproduce
Steps to reproduce the behavior:
Failure logs
-Cut and past the appropriate build messages from the console output.
-Please attach any additional failure logs mentioned in the console output.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
The text was updated successfully, but these errors were encountered: