Re: [boost] [1.56.0] Release candidates available

newer
Hangs with Boost 1.56 on clang...

older
Re: [boost] b2 headers is...

Eric Niebler

29 Jul 2014 29 Jul '14

10:33 p.m.

On 07/29/2014 02:44 PM, Boris Schäling wrote:

...

On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow wrote:

...
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/

I get a compiler error with g++ 4.8.3 on Cygwin (64-bit):

In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf); ^

This looks like the bug Eric had reported at https://svn.boost.org/trac/boost/ticket/10137.

Crud. Beman, did a merge get missed? Eric

Show replies by date

Beman Dawes

30 Jul 30 Jul

1:59 p.m.

New subject: [1.56.0] Release candidates available

On Tue, Jul 29, 2014 at 6:33 PM, Eric Niebler wrote:

...

On 07/29/2014 02:44 PM, Boris Schäling wrote:

...
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow wrote:

...
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/

I get a compiler error with g++ 4.8.3 on Cygwin (64-bit):

In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf); ^

This looks like the bug Eric had reported at https://svn.boost.org/trac/boost/ticket/10137.

Crud. Beman, did a merge get missed?

I'll look at this in a few hours. --Beman

Beman Dawes

9:42 p.m.

New subject: [1.56.0] Release candidates available

On Tue, Jul 29, 2014 at 6:33 PM, Eric Niebler wrote:

...

On 07/29/2014 02:44 PM, Boris Schäling wrote:

...
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow wrote:

...
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/

I get a compiler error with g++ 4.8.3 on Cygwin (64-bit):

In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf); ^

This looks like the bug Eric had reported at https://svn.boost.org/trac/boost/ticket/10137.

Crud. Beman, did a merge get missed?

It was a pull request. I've merged it to develop, although I only tested it on VC++ and MinGW because I'm having trouble getting Cygwin tests to work because of some flaw in my test setup. I'll take a break, then look at it again. But even if it is working for Cygwin, I'd want to see successful tests on Linux and OS X at a minimum before merging to master. --Beman

Beman Dawes

2 Aug 2 Aug

12:36 p.m.

New subject: [1.56.0] Release candidates available

On Wed, Jul 30, 2014 at 5:42 PM, Beman Dawes wrote:

...

On Tue, Jul 29, 2014 at 6:33 PM, Eric Niebler wrote:

...
On 07/29/2014 02:44 PM, Boris Schäling wrote:

...
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow wrote:

...
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/

I get a compiler error with g++ 4.8.3 on Cygwin (64-bit):

In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf); ^

This looks like the bug Eric had reported at https://svn.boost.org/trac/boost/ticket/10137.

Crud. Beman, did a merge get missed?

It was a pull request. I've merged it to develop, although I only tested it on VC++ and MinGW because I'm having trouble getting Cygwin tests to work because of some flaw in my test setup. I'll take a break, then look at it again.

But even if it is working for Cygwin, I'd want to see successful tests on Linux and OS X at a minimum before merging to master.

I've now tested Boost.System locally: OS X / gcc OS X / clang Ubuntu / gcc Ubuntu / clang Win 7 / msvc-10.0 Win 7 / msvc-11.0 Win 7 / msvc-12.0 Win 7 / gcc - cygwin / cygwin installer / from bash (thanks to Eric for help getting this running) Win 7 / gcc - cygwin / cygwin installer / from Windows command line Win 7 / gcc - mingw / mingw installer / from Windows command line The last two turned up a different configuration issue which has also been fixed. I'd like permission to merge system develop to master Sunday morning (after more regression testers have cycled)> --Beman

Tom Kent

3:27 p.m.

New subject: [1.56.0] Release candidates available

On Sat, Aug 2, 2014 at 7:36 AM, Beman Dawes wrote:

...

I'd like permission to merge system develop to master Sunday morning (after more regression testers have cycled)

Assuming that happens are we going to give a couple more days for master testers to cycle before pushing another rc? Tom

Kyle Ketterer

5:44 p.m.

New subject: [1.56.0] Release candidates available

I have successfully compiled this RC on Win76 using Mingw and Mingw64 (win builds) : b2 toolset=gcc --build-type=complete stage /* address-model=64 */

Kyle Ketterer

5:45 p.m.

New subject: [1.56.0] Release candidates available

On Sat, Aug 2, 2014 at 1:44 PM, Kyle Ketterer wrote:

...

I have successfully compiled this RC on Win76 using Mingw and Mingw64 (win builds) :

b2 toolset=gcc --build-type=complete stage /* address-model=64 */

* Win7 x64

Niall Douglas

11:34 p.m.

New subject: [1.56.0] Release candidates available

On 2 Aug 2014 at 13:44, Kyle Ketterer wrote:

...

I have successfully compiled this RC on Win76 using Mingw and Mingw64 (win builds) :

b2 toolset=gcc --build-type=complete stage /* address-model=64 */

I would be highly surprised if rc1 compiles with mingw32. A fix of mine which entered rc1 broke mingw32. I pushed a fix today to develop branch. I don't see it as a showstopper as mingw-w64 still works, and besides ASIO hasn't compiled with mingw32 without a bit of prodding for over a year and no one complains, they just follow the stackoverflow guide. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

Kyle Ketterer

3 Aug 3 Aug

12:39 a.m.

New subject: [1.56.0] Release candidates available

...

I would be highly surprised if rc1 compiles with mingw32. A fix of mine which entered rc1 broke mingw32.

I pushed a fix today to develop branch. I don't see it as a showstopper as mingw-w64 still works, and besides ASIO hasn't compiled with mingw32 without a bit of prodding for over a year and no one complains, they just follow the stackoverflow guide.

Niall

Nail, I apologize for the confusion. The Win-Builds project has a 32 bit and 64 bit tool set. I mistakenly referred to this as THE Mingw. I was able to compile this RC with the 32 and 64 bit toolset of that distro. Keep up the excellent work !

3770

Age (days ago)

3775

Last active (days ago)

List overview

Download

8 comments

5 participants

participants (5)

Beman Dawes
Eric Niebler
Kyle Ketterer
Niall Douglas
Tom Kent