[release] Boost 1.81.0 Beta 1 Release Candidate 1 is available
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/ The SHA256 checksums are as follows: 6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers
On Nov 10, 2022, at 9:00 AM, Marshall Clow
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Successfully built the libraries in Mac OS 12.6.1, with "Apple clang version 14.0.0 (clang-1400.0.29.202)” and C++ 03/11/14/17/2a, on both x86 and ARM. Lots of warnings about sprintf, though: ./boost/test/utils/setcolor.hpp:92:31: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations] m_command_size = std::sprintf( m_control_command, "%c[%c;3%c;4%cm", ^ /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:188:1: note: 'sprintf' has been explicitly marked deprecated here __deprecated_msg("This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.") ^ /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg' #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg))) ^ — Marshall
On Thu, Nov 10, 2022 at 11:00 AM Marshall Clow via Boost < boost@lists.boost.org> wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
-- The Release Managers
Looks good on Visual Studio/Windows. toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X msvc-14.2 32 X X X msvc-14.2 64 X X X msvc-14.3 32 X X X msvc-14.3 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. See full results here: https://gist.github.com/teeks99/aa970713d986dff96dd2787ef7a387ff Tom
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line: #define Opposite 4 This is a regression from Boost version 1.80.0. -- Rainer Deyke (rainerd@eldwood.com)
On 11/11/22 19:59, Rainer Deyke via Boost wrote:
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line:
#define Opposite 4
This is a regression from Boost version 1.80.0.
X.org headers define quite a few macros like this. I did have name clashes between X.org headers and other libraries (non-Boost) before, and I'm of the opinion it is X.org that needs to be fixed. Unfortunately, given that it is barely maintained, people will likely have to work around this until it dies out. Bottom line, this problem isn't new, and IMHO is not worth fixing in Boost. Of course, it is up to Boost.JSON maintainers to decide.
On Nov 11, 2022, at 8:59 AM, Rainer Deyke via Boost
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/ The SHA256 checksums are as follows: 6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line:
#define Opposite 4
This is a regression from Boost version 1.80.0.
I have created https://github.com/boostorg/json/issues/803 https://github.com/boostorg/json/issues/803 to track this. — Marshall
Fixed on develop now. By the way, does anyone have a good list of such
names to avoid? I'd like to make a test for it.
пт, 11 нояб. 2022 г. в 19:59, Rainer Deyke via Boost
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line:
#define Opposite 4
This is a regression from Boost version 1.80.0.
-- Rainer Deyke (rainerd@eldwood.com)
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Fri, Nov 11, 2022 at 3:08 PM Дмитрий Архипов via Boost
Fixed on develop now. By the way, does anyone have a good list of such names to avoid? I'd like to make a test for it.
I have a second-hand report that "T" is one such name. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
On Fri, Nov 11, 2022, at 10:10 PM, René Ferdinand Rivera Morell via Boost wrote:
I have a second-hand report that "T" is one such name.
Yeah I dealt with this X.h infection before and it was really basic, common identifiers. I do not have access to the proprietary code base anymore, but I think I remember multiple names like `type` being involved. We ended up deciding it couldn't be done, and the X.h header must be limited to specific TUs that can the conflicts.
That is a well-known problem in X.h.
From experience it has many (many) more of these and it's not some other library's fault. It should be fixed in X.h.
I've tried to comb through corporate headers to work with X.h after GPU code was introduced in headers. The only working solution in the end was (a) to hide all use of X.h from headers (b) even creating platform specific minified headers for GPU-aware parts of the code base. I remember seeing mozilla/firefox tickets about this exact problem with these ancient headers. Perhaps they have more detailed strategies to deal with it in your project. It's annoying, but it clearly has little to do with Boost or Boost JSON. Regards, Seth On Fri, Nov 11, 2022, at 5:59 PM, Rainer Deyke via Boost wrote:
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line:
#define Opposite 4
This is a regression from Boost version 1.80.0.
-- Rainer Deyke (rainerd@eldwood.com)
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (8)
-
Andrey Semashev -
Marshall Clow -
Rainer Deyke -
René Ferdinand Rivera Morell -
Seth -
Tom Kent -
Vinnie Falco -
Дмитрий Архипов