Build Issue - URL - msvc-14.0
In preparation for the upcoming lockdown and release, I just grabbed the latest snapshot from here: https://boostorg.jfrog.io/artifactory/main/master/boost_1_81_0-snapshot.tar.... I ran it through the build process and got some issues with boost::url running on msvc-14.0. Some examples of them are: D:\RB\boost_1_81_0\boost/url/param.hpp(886): error C2134: 'boost::urls::grammar::string_view_base::string_view_base': call does not result in a constant expression D:\RB\boost_1_81_0\boost/url/param.hpp(886): note: failure was caused by call of undefined function or one not declared 'constexpr' The full output log is here: https://gist.github.com/teeks99/8d14da5b50cffda13f9ad5e23a8d80aa Tom
On Fri, Oct 28, 2022 at 7:04 PM Tom Kent via Boost
I ran it through the build process and got some issues with boost::url running on msvc-14.0.
Sorry about that. It turns out that msvc-14.0 doesn't have enough conforming C++11 constexpr to support Boost.URL. We have made some fixes to the build and CI scripts to indicate this, we might need more (or the snapshot might not have the fixes). Thanks
On Sat, Oct 29, 2022 at 12:05 AM Vinnie Falco
On Fri, Oct 28, 2022 at 7:04 PM Tom Kent via Boost
wrote: I ran it through the build process and got some issues with boost::url running on msvc-14.0.
Sorry about that. It turns out that msvc-14.0 doesn't have enough conforming C++11 constexpr to support Boost.URL. We have made some fixes to the build and CI scripts to indicate this, we might need more (or the snapshot might not have the fixes).
I'm still seeing this issue on the latest nightly build. Is it possible this is stuck on develop? Or the rules don't prevent URL from building on msvc-14.0? Tom
On Sat, Nov 5, 2022 at 10:09 AM Tom Kent
I'm still seeing this issue on the latest nightly build. Is it possible this is stuck on develop? Or the rules don't prevent URL from building on msvc-14.0?
I'm pretty sure we updating both develop and master to exclude msvc-14.0: https://github.com/boostorg/url/blob/develop/meta/explicit-failures-markup.x... https://github.com/boostorg/url/blob/master/meta/explicit-failures-markup.xm... Maybe we need to do more? I don't know, but the matrix looks like it is being excluded. Thanks
Vinnie Falco wrote:
On Sat, Nov 5, 2022 at 10:09 AM Tom Kent
wrote: I'm still seeing this issue on the latest nightly build. Is it possible this is stuck on develop? Or the rules don't prevent URL from building on msvc-14.0?
I'm pretty sure we updating both develop and master to exclude msvc-14.0:
https://github.com/boostorg/url/blob/develop/meta/explicit-failures- markup.xml#L22 https://github.com/boostorg/url/blob/master/meta/explicit-failures- markup.xml#L22
Maybe we need to do more? I don't know, but the matrix looks like it is being excluded.
You need to fix your Jamfile to disable the library for msvc-14.0, because your current checks do not exclude it. Add <toolset>msvc-14.0:<build>no either somewhere here https://github.com/boostorg/url/blob/643d959e3db8b59cf3f065ec1738cd0197c70b0... or here https://github.com/boostorg/url/blob/643d959e3db8b59cf3f065ec1738cd0197c70b0... C:\boost-git\develop\libs\url>b2 build toolset=msvc-14.0 Performing configuration checks - default address-model : 64-bit (cached) [1] - default architecture : x86 (cached) [1] - symlinks supported : yes (cached) - cxx11_constexpr : yes (cached) [2] - cxx11_decltype : yes (cached) [2] - cxx11_hdr_tuple : yes [2] - cxx11_template_aliases : yes [2] - cxx11_variadic_templates : yes [2] - cxx11_constexpr : yes (cached) [3] - cxx11_decltype : yes (cached) [3] - cxx11_hdr_tuple : yes (cached) [3] - cxx11_template_aliases : yes (cached) [3] - cxx11_variadic_templates : yes (cached) [3] [1] msvc-14.0 [2] msvc-14.0/debug/python-2.7/threadapi-pthread/threading-multi/visibility-hidden [3] msvc-14.0/debug/python-2.7/threadapi-win32/threading-multi/visibility-hidden ...patience... ...found 1343 targets... ...updating 9 targets... compile-c-c++ ..\..\bin.v2\libs\url\build\msvc-14.0\debug\threading-multi\src.obj src.cpp C:\boost-git\develop\boost/url/grammar/lut_chars.hpp(262): warning C4800: 'uint64_t': forcing value to bool 'true' or 'false' (performance warning) C:\boost-git\develop\boost/url/grammar/detail/tuple.hpp(83): warning C4814: 'boost::urls::grammar::detail::tuple_element_impl::get': in C++14 'constexpr' will not imply 'const'; consider explicitly specifying 'const' C:\boost-git\develop\boost/url/grammar/detail/tuple.hpp(91): note: see reference to class template instantiation 'boost::urls::grammar::detail::tuple_element_impl' being compiled C:\boost-git\develop\boost/url/param.hpp(886): error C2134: 'boost::urls::grammar::string_view_base::string_view_base': call does not result in a constant expression C:\boost-git\develop\boost/url/param.hpp(886): note: failure was caused by call of undefined function or one not declared 'constexpr' C:\boost-git\develop\boost/url/grammar/string_view_base.hpp(72): note: see declaration of 'boost::urls::grammar::string_view_base::string_view_base' C:\boost-git\develop\boost/url/rfc/pchars.hpp(45): error C2127: 'boost::urls::pchars': illegal initialization of 'constexpr' entity with a non-constant expression C:\boost-git\develop\boost/url/grammar/lut_chars.hpp(300): note: a non-constant (sub-)expression was encountered
participants (3)
-
Peter Dimov
-
Tom Kent
-
Vinnie Falco