[release] Boost 1.68.0 Beta 1 Release Candidate 1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
The release candidates for the first 1.68.0 beta release are now available
at:

<https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>

The release notes are not yet available.
The updated documentation is not yet available.
[ They will be available in a day or two. ]

The SHA256 checksums are as follows:

4b39978aa227f56cc00715d48032e18f4bb259de756637a653b5acead4417e0b
boost_1_68_0_b1_rc1.7z
39f6fdc16fc62041ca1401c5e8d1cd0220de24fd5d909eca3f0bf1049d1fd6f9
boost_1_68_0_b1_rc1.tar.bz2
9714d11a205e6f3a1cf1ed17b0caad8a64bc4a5459dfc6e1629e14e5e4b44dc7
boost_1_68_0_b1_rc1.tar.gz
fe35f20eb5c2ebf5d4e4f15d0416e484058a732ca1a1e59b831b79d4d7702bdd
boost_1_68_0_b1_rc1.zip

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 Boost Release Managers

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On Thu, Jul 5, 2018 at 7:55 PM, Marshall Clow <[hidden email]> wrote:

> The release candidates for the first 1.68.0 beta release are now available
> at:
>
> <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
>
> The release notes are not yet available.
> The updated documentation is not yet available.
> [ They will be available in a day or two. ]
>
> The SHA256 checksums are as follows:
>
> 4b39978aa227f56cc00715d48032e18f4bb259de756637a653b5acead4417e0b
> boost_1_68_0_b1_rc1.7z
> 39f6fdc16fc62041ca1401c5e8d1cd0220de24fd5d909eca3f0bf1049d1fd6f9
> boost_1_68_0_b1_rc1.tar.bz2
> 9714d11a205e6f3a1cf1ed17b0caad8a64bc4a5459dfc6e1629e14e5e4b44dc7
> boost_1_68_0_b1_rc1.tar.gz
> fe35f20eb5c2ebf5d4e4f15d0416e484058a732ca1a1e59b831b79d4d7702bdd
> boost_1_68_0_b1_rc1.zip
>
> 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 have successfully built the rc1 release on Mac OS 10.13 with Apple clang
9.1
(c++03/c++11/c++14/c++17/c++2a)

-- Marshall

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Jul 5, 2018 at 9:55 PM, Marshall Clow via Boost <
[hidden email]> wrote:

> The release candidates for the first 1.68.0 beta release are now available
> at:
>
> <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
>

I see that the path formula has changed (a separate .rc1 directory), is
this going to persist for the release RCs as well? I just want to update my
scripts to point to the right place :-)

Thanks,
Tom

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
On Fri, Jul 6, 2018 at 4:26 AM, Tom Kent via Boost <[hidden email]>
wrote:

> On Thu, Jul 5, 2018 at 9:55 PM, Marshall Clow via Boost <
> [hidden email]> wrote:
>
> > The release candidates for the first 1.68.0 beta release are now
> available
> > at:
> >
> > <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
> >
>
> I see that the path formula has changed (a separate .rc1 directory), is
> this going to persist for the release RCs as well? I just want to update my
> scripts to point to the right place :-)
>
>
The extra dot (".1.rc1") was me fat-fingering.
But yeah, I was planning on having an RC1/RC2/<naked> directory.

-- Marshall

P.S. Sorry for the noise. I haven't figured out how to automate the bintray
bits yet. When I do I will let you know.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Fri, Jul 6, 2018 at 6:28 AM, Tom Kent <[hidden email]> wrote:

>
>
> On Thu, Jul 5, 2018 at 9:55 PM, Marshall Clow via Boost <
> [hidden email]> wrote:
>
>> The release candidates for the first 1.68.0 beta release are now available
>> at:
>>
>> <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
>>
>> [ snipped ]


> - It looks like boost/version.hpp hasn't been updated for 1.68. It still
> has two instances of "67" in it, which seem to be cause the auto-linking
> features for visual studio to look for *-1_67.lib files, while the ones
> generated are *-1_68.lib. This is present in all four archive formats.
> Showstopper.
>

I agree - that's worth rolling an RC2 for.
It was changed in develop, but not merged to master.

- Tests for Windows/Visual Studio builds failed for msvc-10.0 in program
> options:


I've pinged Vladmir about the program_options problem.

-- Marshall

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 06/07/2018 16:28, Tom Kent via Boost-users wrote:

> - Tests for Windows/Visual Studio builds failed for msvc-10.0 in program options:
>
> compile-c-c++ bin.v2\libs\program_options\build\msvc-10.0\debug\link-static\runtime-link-static\threading-multi\options_description.obj
> options_description.cpp
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\utility(163) : error C2440: 'initializing' : cannot convert from 'int' to 'const std::basic_string<_Elem,_Traits,_Ax> '

It seems that MSVC 10 cannot handle this:

        std::pair<const std::string*, size_t>(NULL, 0)

I've pushed a potential fix to master. It probably does not warrant holding a beta, as later versions
of MSVC are fine.

- Volodya



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
(previous mail sent to boost-users@ by mistake)

Marshall Clow via Boost <[hidden email]> writes:

> The release candidates for the first 1.68.0 beta release are now available
> at:
>
> <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>

Fails to build on FreeBSD because https://github.com/boostorg/wave/pull/31
despite being merged months ago is not included in rc1.

In file included from libs/wave/src/instantiate_re2c_lexer.cpp:29:
In file included from ./boost/wave/cpplexer/re2clex/cpp_re2c_lexer.hpp:38:
In file included from ./boost/wave/cpplexer/re2clex/cpp_re.hpp:379:
cpp.re:189:7: error: cannot initialize return object of type 'boost::wave::token_id' with an rvalue of type 'int'
    { BOOST_WAVE_RET(T_DIVIDE); }
      ^~~~~~~~~~~~~~~~~~~~~~~~
./boost/wave/cpplexer/re2clex/cpp_re.hpp:65:16: note: expanded from macro 'BOOST_WAVE_RET'
        return (i);                                                           \
               ^~~
1 error generated.

Full build log: https://ptpb.pw/qWiz

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
Built on Fedora 28, gcc 8.1.1. Used the default settings. The build
generally passes, .a and .so files get built, but I get errors when
compiling the python module:


```
...failed gcc.compile.c++
bin.v2/libs/python/build/gcc-8.1.1/release/threading-multi/object_protocol.o...
gcc.compile.c++
bin.v2/libs/python/build/gcc-8.1.1/release/threading-multi/object_operators.o
In file included from ./boost/python/detail/prefix.hpp:13,
                 from ./boost/python/object_operators.hpp:8,
                 from libs/python/src/object_operators.cpp:6:
./boost/python/detail/wrap_python.hpp:50:11: fatal error: pyconfig.h: No
such file or directory
 # include <pyconfig.h>
           ^~~~~~~~~~~~
compilation terminated.

    "g++"   -fPIC -m64 -pthread -O3 -finline-functions -Wno-inline -Wall
-DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG  -I"."
-I"/usr/include/python2.7" -c -o
"bin.v2/libs/python/build/gcc-8.1.1/release/threading-multi/object_operators.o"
"libs/python/src/object_operators.cpp"
```

The same problem was reported when testing the previous release:
https://groups.google.com/d/msg/boost-developers-archive/h7JLVXgt6Kg/acrsoa3HAQAJ

This happens when I have python installed but not python-devel.

When I build with `--without-libraries=python` everything is fine.

Regards,
&rzej;

2018-07-06 4:55 GMT+02:00 Marshall Clow via Boost <[hidden email]>:

> The release candidates for the first 1.68.0 beta release are now available
> at:
>
> <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
>
> The release notes are not yet available.
> The updated documentation is not yet available.
> [ They will be available in a day or two. ]
>
> The SHA256 checksums are as follows:
>
> 4b39978aa227f56cc00715d48032e18f4bb259de756637a653b5acead4417e0b
> boost_1_68_0_b1_rc1.7z
> 39f6fdc16fc62041ca1401c5e8d1cd0220de24fd5d909eca3f0bf1049d1fd6f9
> boost_1_68_0_b1_rc1.tar.bz2
> 9714d11a205e6f3a1cf1ed17b0caad8a64bc4a5459dfc6e1629e14e5e4b44dc7
> boost_1_68_0_b1_rc1.tar.gz
> fe35f20eb5c2ebf5d4e4f15d0416e484058a732ca1a1e59b831b79d4d7702bdd
> boost_1_68_0_b1_rc1.zip
>
> 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 Boost Release Managers
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/
> mailman/listinfo.cgi/boost
>

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] Boost 1.68.0 Beta 1 Release Candidate 1

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Fri, Jul 6, 2018 at 4:26 AM, Tom Kent via Boost <[hidden email]>
wrote:

> On Thu, Jul 5, 2018 at 9:55 PM, Marshall Clow via Boost <
> [hidden email]> wrote:
>
> > The release candidates for the first 1.68.0 beta release are now
> available
> > at: <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/>
>
> I see that the path formula has changed (a separate .rc1 directory), is
> this going to persist for the release RCs as well? I just want to update my
> scripts to point to the right place :-)
>
>
Next release is at:
     https://dl.bintray.com/boostorg/beta/1.68.0.beta1.rc2/
(missing the extra '.')

-- Marshall

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost