[release] Boost 1.71.0 Release Candidate 2 available

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[release] Boost 1.71.0 Release Candidate 2 available

Boost - Dev mailing list
The release candidates for the 1.71.0 release are now available at:
<https://dl.bintray.com/boostorg/release/1.71.0/source/>

The SHA256 checksums are as follows:

1b3949ffddf56129141032542523920034f2e69775fb9332a52ba37c548dbf35
boost_1_71_0_rc2.7z

d73a8da01e8bf8c7eda40b4c84915071a8c8a0df4a6734537ddde4a8580524ee
boost_1_71_0_rc2.tar.bz2

96b34f7468f26a141f6020efb813f1a2f3dfb9797ecf76a7d7cbd843cc95f5bd
boost_1_71_0_rc2.tar.gz

85a94ac71c28e59cf97a96714e4c58a18550c227ac8b0388c260d6c717e47a69
boost_1_71_0_rc2.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.71.0 Release Candidate 2 available

Boost - Dev mailing list
On 14/08/2019 18:29, Michael Caisse via Boost wrote:
> 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.

Yay, Outcome now runs its unit tests and all pass (well, except one on
my version of MSVC, which has a compiler bug).

Thanks to Rene for the timely fix to Predef and to Michael for holding
up the release to get this fixed.

Niall

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

Re: [release] Boost 1.71.0 Release Candidate 2 available

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list

> 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 tried to build it on Ubuntu 18.04 with GCC 8 and C++17, with support
for LibICU enabled, and got the following error:

```
  error: Name clash for
'<p/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8/lib/x86_64-linux-gnu>libboost_filesystem-gcc8-mt-x64-1_71.so.1.71.0'
  error:
  error: Tried to build the target twice, with property sets having
  error: these incompatible properties:
  error:
  error:     -  none
  error:     -  <dll-path>/opt/BENOCS/gcc8/bin
<linkflags>-L/opt/BENOCS/gcc8/lib/x86_64-linux-gnu <linkflags>-licudata
<linkflags>-licui18n <linkflags>-licuuc
  error:
  error: Please make sure to have consistent requirements for these
  error: properties everywhere in your project, especially for install
  error: targets.
```

My build-settings were the following:

```
CFLAGS   = -m64 -fpic -fdiagnostics-color=always -O3 -g
CXXFLAGS = -m64 -fpic -fdiagnostics-color=always -O3 -g -std=c++17
LDFLAGS  = -Wl,--as-needed

b2 -j4 -q \
 
--build-dir="/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/build/boost"
\
  --build-type=minimal \
  --layout=versioned \
  address-model=64 \
  install \
 
--prefix="/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8"
\
 
--libdir="/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8/lib/x86_64-linux-gnu"
\
  dll-path="/opt/BENOCS/gcc8/lib/x86_64-linux-gnu" \
  -sICU_PATH="/opt/BENOCS/gcc8" \
  -sICU_LINK="-L/opt/BENOCS/gcc8/lib/x86_64-linux-gnu -licuuc -licudata
-licui18n" \
  toolset=gcc-8 \
  cflags="${CFLAGS}" \
  cxxflags="${CXXFLAGS}" \
  linkflags="${LDFLAGS}"
```

The Boost configuration-checks resulted in:

```
  Performing configuration checks

      - default address-model    : 64-bit
      - default architecture     : x86
      - C++11 mutex              : yes
      - lockfree boost::atomic_flag : yes
      - Boost.Config Feature Check: cxx11_auto_declarations : yes
      - Boost.Config Feature Check: cxx11_constexpr : yes
      - Boost.Config Feature Check: cxx11_defaulted_functions : yes
      - Boost.Config Feature Check: cxx11_final : yes
      - Boost.Config Feature Check: cxx11_hdr_mutex : yes
      - Boost.Config Feature Check: cxx11_hdr_tuple : yes
      - Boost.Config Feature Check: cxx11_lambdas : yes
      - Boost.Config Feature Check: cxx11_noexcept : yes
      - Boost.Config Feature Check: cxx11_nullptr : yes
      - Boost.Config Feature Check: cxx11_rvalue_references : yes
      - Boost.Config Feature Check: cxx11_template_aliases : yes
      - Boost.Config Feature Check: cxx11_thread_local : yes
      - Boost.Config Feature Check: cxx11_variadic_templates : yes
      - has_icu builds           : yes
  warning: non-free usage requirements <runtime-link>shared ignored
  warning: in main-target icu_options at libs/regex/build/Jamfile.v2:97
  warning: Graph library does not contain MPI-based parallel components.
  note: to enable them, add "using mpi ;" to your user-config.jam.
  note: to suppress this message, pass "--without-graph_parallel" to bjam.
      - zlib                     : yes
      - bzip2                    : yes
      - lzma                     : no
      - zstd                     : no
      - iconv (libc)             : yes
      - icu                      : yes
      - native-atomic-int32-supported : yes
      - native-syslog-supported  : yes
      - pthread-supports-robust-mutexes : yes
      - compiler-supports-ssse3  : yes
      - compiler-supports-avx2   : yes
      - gcc visibility           : yes
      - long double support      : yes
  warning: skipping optional Message Passing Interface (MPI) library.
  note: to enable MPI support, add "using mpi ;" to user-config.jam.
  note: to suppress this message, pass "--without-mpi" to bjam.
  note: otherwise, you can safely ignore this message.
      - libbacktrace builds      : yes
      - addr2line builds         : yes
      - WinDbg builds            : no
      - WinDbgCached builds      : no
      - BOOST_COMP_GNUC >= 4.3.0 : yes
      - zlib                     : yes
      - bzip2                    : yes
      - lzma                     : no
      - zstd                     : no
```

Either I did something completely wrong or the configuration files of
Boost.FileSystem are inconsistent regarding some compiler-flags!?

Hope that is helpful,
Deniz


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

Re: [release] Boost 1.71.0 Release Candidate 2 available

Boost - Dev mailing list
On Thu, Aug 15, 2019 at 2:39 PM Deniz Bahadir via Boost
<[hidden email]> wrote:

>
> > 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 tried to build it on Ubuntu 18.04 with GCC 8 and C++17, with support
> for LibICU enabled, and got the following error:
>
> ```
>   error: Name clash for
> '<p/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8/lib/x86_64-linux-gnu>libboost_filesystem-gcc8-mt-x64-1_71.so.1.71.0'
>   error:
>   error: Tried to build the target twice, with property sets having
>   error: these incompatible properties:
>   error:
>   error:     -  none
>   error:     -  <dll-path>/opt/BENOCS/gcc8/bin
> <linkflags>-L/opt/BENOCS/gcc8/lib/x86_64-linux-gnu <linkflags>-licudata
> <linkflags>-licui18n <linkflags>-licuuc
>   error:
>   error: Please make sure to have consistent requirements for these
>   error: properties everywhere in your project, especially for install
>   error: targets.
> ```
>
> Either I did something completely wrong or the configuration files of
> Boost.FileSystem are inconsistent regarding some compiler-flags!?

Boost.Filesystem Jamfile doesn't use the properties listed in the
error message and I don't see anything wrong with the Jamfile. My
guess is that there is some sort of a dependency from another library
that messes up these properties, but it is not clear from the message
what that other library is. Or maybe there's a different problem. A
Boost.Build magician is needed.

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

Re: [release] Boost 1.71.0 Release Candidate 2 available

Boost - Dev mailing list
Am 15.08.19 um 22:18 schrieb Andrey Semashev via Boost:

> On Thu, Aug 15, 2019 at 2:39 PM Deniz Bahadir via Boost
> <[hidden email]> wrote:
>>
>>> 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 tried to build it on Ubuntu 18.04 with GCC 8 and C++17, with support
>> for LibICU enabled, and got the following error:
>>
>> ```
>>    error: Name clash for
>> '<p/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8/lib/x86_64-linux-gnu>libboost_filesystem-gcc8-mt-x64-1_71.so.1.71.0'
>>    error:
>>    error: Tried to build the target twice, with property sets having
>>    error: these incompatible properties:
>>    error:
>>    error:     -  none
>>    error:     -  <dll-path>/opt/BENOCS/gcc8/bin
>> <linkflags>-L/opt/BENOCS/gcc8/lib/x86_64-linux-gnu <linkflags>-licudata
>> <linkflags>-licui18n <linkflags>-licuuc
>>    error:
>>    error: Please make sure to have consistent requirements for these
>>    error: properties everywhere in your project, especially for install
>>    error: targets.
>> ```
>>
>> Either I did something completely wrong or the configuration files of
>> Boost.FileSystem are inconsistent regarding some compiler-flags!?
>
> Boost.Filesystem Jamfile doesn't use the properties listed in the
> error message and I don't see anything wrong with the Jamfile. My
> guess is that there is some sort of a dependency from another library
> that messes up these properties, but it is not clear from the message
> what that other library is. Or maybe there's a different problem. A
> Boost.Build magician is needed.
>

I tested Boost 1.70.0 and 1.69.0 and realized that this error was
introduced with Boost 1.70.0.
Maybe that helps in nailing the source of error down?

Deniz

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

Re: [release] Boost 1.71.0 Release Candidate 2 available

Boost - Dev mailing list
Am 16.08.19 um 14:30 schrieb Deniz Bahadir:

> Am 15.08.19 um 22:18 schrieb Andrey Semashev via Boost:
>> On Thu, Aug 15, 2019 at 2:39 PM Deniz Bahadir via Boost
>> <[hidden email]> wrote:
>>>
>>>> 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 tried to build it on Ubuntu 18.04 with GCC 8 and C++17, with support
>>> for LibICU enabled, and got the following error:
>>>
>>> ```
>>>    error: Name clash for
>>> '<p/home/jenkins/workspace/Pipeline_Boost-1.71.0-rc2/gcc8/installed/opt/BENOCS/gcc8/lib/x86_64-linux-gnu>libboost_filesystem-gcc8-mt-x64-1_71.so.1.71.0'
>>>
>>>    error:
>>>    error: Tried to build the target twice, with property sets having
>>>    error: these incompatible properties:
>>>    error:
>>>    error:     -  none
>>>    error:     -  <dll-path>/opt/BENOCS/gcc8/bin
>>> <linkflags>-L/opt/BENOCS/gcc8/lib/x86_64-linux-gnu <linkflags>-licudata
>>> <linkflags>-licui18n <linkflags>-licuuc
>>>    error:
>>>    error: Please make sure to have consistent requirements for these
>>>    error: properties everywhere in your project, especially for install
>>>    error: targets.
>>> ```
>>>
>>> Either I did something completely wrong or the configuration files of
>>> Boost.FileSystem are inconsistent regarding some compiler-flags!?
>>
>> Boost.Filesystem Jamfile doesn't use the properties listed in the
>> error message and I don't see anything wrong with the Jamfile. My
>> guess is that there is some sort of a dependency from another library
>> that messes up these properties, but it is not clear from the message
>> what that other library is. Or maybe there's a different problem. A
>> Boost.Build magician is needed.
>>
>
> I tested Boost 1.70.0 and 1.69.0 and realized that this error was
> introduced with Boost 1.70.0.
> Maybe that helps in nailing the source of error down?
>

Boost 1.71.0 is released now with this bug. And now I realized that I
was not the first to find that problem. There has been a bug-report in
Github already. [1]

Maybe this problem can be fixed before the next release?

Thanks,
Deniz

[1] https://github.com/boostorg/boost/issues/315

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