[1.48.0] Beta 1 release candidates available

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

[1.48.0] Beta 1 release candidates available

Beman Dawes
Release candidate files for 1.48.0 beta 1 are available at
http://boost.cowic.de/rc/

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.

This helps ensure the candidates build OK before we push them out to
SourceForge.

Thanks,

--The release managers

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
On Wed, Oct 26, 2011 at 3:41 PM, Beman Dawes <[hidden email]> wrote:
> Release candidate files for 1.48.0 beta 1 are available at
> http://boost.cowic.de/rc/

Does it build on VC11?

Olaf

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
In reply to this post by Beman Dawes
On Wed, Oct 26, 2011 at 3:41 PM, Beman Dawes <[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.

1>c:\vc\include\boost\move\move.hpp(28): warning C4005:
'_SCL_SECURE_NO_WARNINGS' : macro redefinition
1>          command-line arguments :  see previous definition of
'_SCL_SECURE_NO_WARNINGS'

Olaf

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

Re: [1.48.0] Beta 1 release candidates available

Владислав Щапов
In reply to this post by Beman Dawes
Hello!

In the version 1.48.0beta1 there was a bug which leads to impossibility to
use at least boost.asio and boost.unordered. Bugreport:
https://svn.boost.org/trac/boost/ticket/6062

And, please, fix a bug of Intel C++ and MSVC2010:
https://svn.boost.org/trac/boost/ticket/5984


2011/10/26 Beman Dawes <[hidden email]>

> Release candidate files for 1.48.0 beta 1 are available at
> http://boost.cowic.de/rc/
>
> 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.
>
> This helps ensure the candidates build OK before we push them out to
> SourceForge.
>
> Thanks,
>
> --The release managers
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>



--
С уважением, Владислав Щапов
ICQ: 223-695-654

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
In reply to this post by Olaf van der Spek-3
On Wed, Oct 26, 2011 at 6:49 PM, Olaf van der Spek <[hidden email]> wrote:
> On Wed, Oct 26, 2011 at 3:41 PM, Beman Dawes <[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.
>
> 1>c:\vc\include\boost\move\move.hpp(28): warning C4005:
> '_SCL_SECURE_NO_WARNINGS' : macro redefinition
> 1>          command-line arguments :  see previous definition of
> '_SCL_SECURE_NO_WARNINGS'

In another project:
1>c:\program files (x86)\microsoft visual studio
10.0\vc\include\iterator(530): error C3859: virtual memory range for
PCH exceeded; please recompile with a command line option of '-Zm110'
or greater
1>c:\program files (x86)\microsoft visual studio
10.0\vc\include\iterator(530): fatal error C1076: compiler limit :
internal heap limit reached; use /Zm to specify a higher limit
1>

Should this be expected with 1.48?

--
Olaf

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

Re: [1.48.0] Beta 1 release candidates available

Lars Viklund
On Wed, Oct 26, 2011 at 07:26:27PM +0200, Olaf van der Spek wrote:
> In another project:
> 1>c:\program files (x86)\microsoft visual studio
> 10.0\vc\include\iterator(530): error C3859: virtual memory range for
> PCH exceeded; please recompile with a command line option of '-Zm110'
> or greater
> 1>c:\program files (x86)\microsoft visual studio
> 10.0\vc\include\iterator(530): fatal error C1076: compiler limit :
> internal heap limit reached; use /Zm to specify a higher limit
> 1>

Is this from building Boost itself? If so, which library?

If it's in your code that uses Boost, it's perfectly natural. When you
build precompiled header files, there's a nice solid chunk of memory
allocated for the compiler to stow away intermediary state in, which it
then serializes to the PCH file, for loading into future compiler
processes that use the precompiled header to bootstrap themselves.

The problem is that this memory needs to be allocated up-front. All this
message means is exactly what it says - the default amount is not
sufficient and you need to change it in the build settings for the
source file that builds your PCH, adding /Zm123 to the advanced compiler
settings field there, or globally for your project.

The reason you get this now and not before is because you've not used
enough Boost libraries, and that the ones you do use have had their
compile-time memory usage increased somewhat.

--
Lars Viklund | [hidden email]

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
On Wed, Oct 26, 2011 at 7:57 PM, Lars Viklund <[hidden email]> wrote:

> On Wed, Oct 26, 2011 at 07:26:27PM +0200, Olaf van der Spek wrote:
>> In another project:
>> 1>c:\program files (x86)\microsoft visual studio
>> 10.0\vc\include\iterator(530): error C3859: virtual memory range for
>> PCH exceeded; please recompile with a command line option of '-Zm110'
>> or greater
>> 1>c:\program files (x86)\microsoft visual studio
>> 10.0\vc\include\iterator(530): fatal error C1076: compiler limit :
>> internal heap limit reached; use /Zm to specify a higher limit
>> 1>
>
> Is this from building Boost itself? If so, which library?
>
> If it's in your code that uses Boost, it's perfectly natural. When you
> build precompiled header files, there's a nice solid chunk of memory
> allocated for the compiler to stow away intermediary state in, which it
> then serializes to the PCH file, for loading into future compiler
> processes that use the precompiled header to bootstrap themselves.

It's my own project. It's the first time ever I see this warning and
it didn't happen with 1.47.

> The problem is that this memory needs to be allocated up-front. All this
> message means is exactly what it says - the default amount is not
> sufficient and you need to change it in the build settings for the
> source file that builds your PCH, adding /Zm123 to the advanced compiler
> settings field there, or globally for your project.
>
> The reason you get this now and not before is because you've not used
> enough Boost libraries, and that the ones you do use have had their
> compile-time memory usage increased somewhat.

Hmm, right. Maybe it's time for MS to increase the default. :p


--
Olaf

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

Re: [1.48.0] Beta 1 release candidates available

Stephan T. Lavavej-2
In reply to this post by Olaf van der Spek-3
[Olaf van der Spek]
> Does it build on VC11?

It successfully built with my current build of VC11 x86 (newer than the Developer Preview, with STL hacking not yet checked in - always good to know that I won't break Boost).

Stephan T. Lavavej
Visual C++ Libraries Developer

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

Re: [1.48.0] Beta 1 release candidates available

Stephan T. Lavavej-2
In reply to this post by Olaf van der Spek-3
[Lars Viklund]
> The problem is that this memory needs to be allocated up-front. All this
> message means is exactly what it says - the default amount is not
> sufficient and you need to change it in the build settings for the
> source file that builds your PCH, adding /Zm123 to the advanced compiler
> settings field there, or globally for your project.

[Olaf van der Spek]
> Hmm, right. Maybe it's time for MS to increase the default. :p

The default is 75 MB on x86 (and 750 MB on x64), which is a fair amount of memory.  Including all STL headers in VC10 SP1 consumed only 29.3 MB when I last measured it.

This has been increased to 83 MB in VC11 as of right now.

STL

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
On Thu, Oct 27, 2011 at 12:02 AM, Stephan T. Lavavej
<[hidden email]> wrote:
> [Olaf van der Spek]
>> Hmm, right. Maybe it's time for MS to increase the default. :p
>
> The default is 75 MB on x86 (and 750 MB on x64), which is a fair amount of memory.  Including all STL headers in VC10 SP1 consumed only 29.3 MB when I last measured it.

Hmm, I'm on x64 but I'm compiling x86 code. What compiler does that use?

> This has been increased to 83 MB in VC11 as of right now.

Why 11?

--
Olaf

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

Re: [1.48.0] Beta 1 release candidates available

Stephan T. Lavavej-2
[Olaf van der Spek]
> Hmm, I'm on x64 but I'm compiling x86 code. What compiler does that use?

The x86-native compiler. VC10 also has an x86=>x64 cross-compiler, and an x64-native compiler (this is the one that reserves tons of address space for its PCH, because it can). Additionally, VC10 had x86=>IA-64 cross, and VC11 has x86=>ARM cross.

(If all of our compilers were x64-hosted, then PCH size problems would vanish in a puff of smoke.)

[STL]
> This has been increased to 83 MB in VC11 as of right now.

[Olaf van der Spek]
> Why 11?

As the compiler changes their data structures, they change the PCH size default accordingly.

STL

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

Re: [1.48.0] Beta 1 release candidates available

Olaf van der Spek-3
On Thu, Oct 27, 2011 at 12:40 AM, Stephan T. Lavavej
<[hidden email]> wrote:

> [Olaf van der Spek]
>> Hmm, I'm on x64 but I'm compiling x86 code. What compiler does that use?
>
> The x86-native compiler. VC10 also has an x86=>x64 cross-compiler, and an x64-native compiler (this is the one that reserves tons of address space for its PCH, because it can). Additionally, VC10 had x86=>IA-64 cross, and VC11 has x86=>ARM cross.
>
> (If all of our compilers were x64-hosted, then PCH size problems would vanish in a puff of smoke.)
>
> [STL]
>> This has been increased to 83 MB in VC11 as of right now.
>
> [Olaf van der Spek]
>> Why 11?
>
> As the compiler changes their data structures, they change the PCH size default accordingly.

So for the end-user the effect is 0?
What's the disadvantage of reserving much more space for the PCH?

--
Olaf

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

Re: [1.48.0] Beta 1 release candidates available

dodheim
In reply to this post by Beman Dawes
Beman Dawes <bdawes <at> acm.org> writes:
> Release candidate files for 1.48.0 beta 1 are available at
> http://boost.cowic.de/rc/
>
> 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.
>
> This helps ensure the candidates build OK before we push them out to
> SourceForge.

No failures or errors when building with MSVC10 SP1, for both 32-bit and 64-bit
builds. However, if it's noteworthy, Wave is giving 'size_t truncated to int'
warnings for 64-bit builds.

Adam


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

Re: [1.48.0] Beta 1 release candidates available

Stephan T. Lavavej-2
In reply to this post by Olaf van der Spek-3
STL> This has been increased to 83 MB in VC11 as of right now.
Olaf> Why 11?
STL> As the compiler changes their data structures, they change the PCH size default accordingly.
Olaf> So for the end-user the effect is 0?

In most cases, yes.

Olaf> What's the disadvantage of reserving much more space for the PCH?

I'm not a compiler dev, but I believe that asking for more memory is more likely to fail - the PCH wants a contiguous block of virtual address space at a certain location. x86 doesn't have that much virtual address space to begin with (and the compiler is already playing a tricky game by asking for the PCH before any other DLLs are loaded).

STL

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

Re: [1.48.0] Beta 1 release candidates available

Hartmut Kaiser
In reply to this post by dodheim
> Beman Dawes <bdawes <at> acm.org> writes:
> > Release candidate files for 1.48.0 beta 1 are available at
> > http://boost.cowic.de/rc/
> >
> > 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.
> >
> > This helps ensure the candidates build OK before we push them out to
> > SourceForge.
>
> No failures or errors when building with MSVC10 SP1, for both 32-bit and
> 64-bit builds. However, if it's noteworthy, Wave is giving 'size_t
> truncated to int'
> warnings for 64-bit builds.

Care to send me the logs (offline)?

Thanks!
Regards Hartmut
---------------
http://boost-spirit.com
http://stellar.cct.lsu.edu




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

Re: [1.48.0] Beta 1 release candidates available

Vicente Botet
In reply to this post by Beman Dawes
Le 26/10/11 15:41, Beman Dawes a écrit :
> Release candidate files for 1.48.0 beta 1 are available at
> http://boost.cowic.de/rc/
>
>
> This helps ensure the candidates build OK before we push them out to
> SourceForge.
>
>
Hi,

Build Ok in Mac OS gcc 4.1.2.

There are some build errors on MAC-OS clang in libraries Locale and Math.

clang-darwin.compile.c++
bin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi/posix/codecvt.o
libs/locale/src/posix/codecvt.cpp:137:30: error: non-constant-expression
cannot be narrowed from type 'unsigned char' to 'char' in initializer list
             char inseq[3] = {seq0 , begin[1], 0};
                              ^~~~
libs/locale/src/posix/codecvt.cpp:137:30: note: override this message by
inserting an explicit cast
             char inseq[3] = {seq0 , begin[1], 0};
                              ^~~~
                              stat)c_cast<char>(
1 error generated.

     "/Users/viboes/clang/llvmCore-3.0-rc1.install/bin/clang++" -x c++
-std=c++0x -O3 -O3 -finline-functions -Wno-inline -Wall
-DBOOST_ALL_NO_LIB=1 -DBOOST_LOCALE_DYN_LINK=1
-DBOOST_LOCALE_NO_WINAPI_BACKEND=1 -DBOOST_LOCALE_WITH_ICONV=1
-DBOOST_THREAD_NO_LIB=1 -DNDEBUG -I"." -c -o
"bin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi/posix/codecvt.o"
"libs/locale/src/posix/codecvt.cpp"

...failed clang-darwin.compile.c++
bin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi/posix/codecvt.o...
...skipped
<pbin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi>libboost_locale.dylib
for lack of
<pbin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi>posix/codecvt.o...
...skipped <pstage/lib>libboost_locale.dylib for lack of
<pbin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi>libboost_locale.dylib...
clang-darwin.compile.c++
bin.v2/libs/math/build/clang-darwin-3.0x/release/threading-multi/cyl_bessel_i.o
In file included from libs/math/build/../src/tr1/cyl_bessel_i.cpp:11:
In file included from ./boost/math/special_functions/bessel.hpp:20:
./boost/math/special_functions/detail/bessel_ik.hpp:320:16: error: call
to function 'bessel_i_small_z_series' that is neither visible in the
template definition nor found by argument-dependent lookup
           Iv = bessel_i_small_z_series(v, x, pol);
                ^
./boost/math/special_functions/bessel.hpp:276:4: note: in instantiation
of function template specialization 'boost::math::detail::bessel_ik<long
double, boost::math::policies::policy<domain_error<errno_on_error>,
pole_error<errno_on_error>, overflow_error<errno_on_error>,
evaluation_error<errno_on_error>, rounding_error<errno_on_error>,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy> >' requested here
    bessel_ik(v, x, &I, &K, need_i, pol);
    ^
./boost/math/special_functions/bessel.hpp:464:65: note: in instantiation
of function template specialization
'boost::math::detail::cyl_bessel_i_imp<long double,
boost::math::policies::policy<domain_error<errno_on_error>,
pole_error<errno_on_error>, overflow_error<errno_on_error>,
evaluation_error<errno_on_error>, rounding_error<errno_on_error>,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy> >' requested here
    return policies::checked_narrowing_cast<result_type,
Policy>(detail::cyl_bessel_i_imp<value_type>(v,
static_cast<value_type>(x), pol),
"boost::math::cyl_bessel_i<%1%>(%1%,%1%)");
                                                                 ^
libs/math/src/tr1/c_policy.hpp:129:1: note: in instantiation of function
template specialization 'boost::math::cyl_bessel_i<double, double,
boost::math::policies::policy<domain_error<errno_on_error>,
pole_error<errno_on_error>, overflow_error<errno_on_error>,
evaluation_error<errno_on_error>, rounding_error<errno_on_error>,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy,
boost::math::policies::default_policy> >' requested here
BOOST_MATH_DECLARE_SPECIAL_FUNCTIONS(c_policy)
^
./boost/math/special_functions/math_fwd.hpp:992:38: note: expanded from:
    cyl_bessel_i(T1 v, T2 x) { return boost::math::cyl_bessel_i(v, x,
Policy()); }\
                                      ^
libs/math/build/../src/tr1/cyl_bessel_i.cpp:16:11: note: in
instantiation of function template specialization
'c_policies::cyl_bessel_i<double, double>' requested here
    return c_policies::cyl_bessel_i BOOST_PREVENT_MACRO_SUBSTITUTION(nu, x);
           ^
./boost/math/special_functions/bessel.hpp:195:10: note:
'bessel_i_small_z_series' should be declared prior to the call site or
in an associated namespace of one of its arguments
inline T bessel_i_small_z_series(T v, T x, const Policy& pol)
          ^
1 error generated.

     "/Users/viboes/clang/llvmCore-3.0-rc1.install/bin/clang++" -x c++
-std=c++0x -O3 -O3 -finline-functions -Wno-inline -Wall
-DBOOST_ALL_NO_LIB=1 -DBOOST_MATH_TR1_DYN_LINK=1 -DNDEBUG -I"."
-I"libs/math/src/tr1" -c -o
"bin.v2/libs/math/build/clang-darwin-3.0x/release/threading-multi/cyl_bessel_i.o"
"libs/math/build/../src/tr1/cyl_bessel_i.cpp"

...failed clang-darwin.compile.c++
bin.v2/libs/math/build/clang-darwin-3.0x/release/threading-multi/cyl_bessel_i.o...


...

The same error appears several times then


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

Re: [1.48.0] Beta 1 release candidates available

Daniel James-3
In reply to this post by Beman Dawes
On 26 October 2011 14:41, Beman Dawes <[hidden email]> wrote:
> Release candidate files for 1.48.0 beta 1 are available at
> http://boost.cowic.de/rc/

I've upload the documentation to the beta site.

(Unfinished) release notes are here:

http://beta.boost.org/users/history/version_1_48_0.html

They're normally linked to from the beta home page, but not at the
moment because I'm half way through changing things. There are a
couple of broken links where the link is hard-coded to a particular
version. I'll look into fixing that later, but for now you can edit
the url yourself; replace /1_48_0/ with /1_48_0_beta1/ and it should
work.

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

Re: [1.48.0] Beta 1 release candidates available

Artyom Beilis
In reply to this post by Vicente Botet
>

> There are some build errors on MAC-OS clang in libraries Locale and Math.
>
> clang-darwin.compile.c++
> bin.v2/libs/locale/build/clang-darwin-3.0x/release/threading-multi/posix/codecvt.o
> libs/locale/src/posix/codecvt.cpp:137:30: error: non-constant-expression cannot
> be narrowed from type 'unsigned char' to 'char' in initializer
> list
>             char inseq[3] = {seq0 , begin[1], 0};
>                              ^~~~
> libs/locale/src/posix/codecvt.cpp:137:30: note: override this message by
> inserting an explicit cast
>             char inseq[3] = {seq0 , begin[1], 0};
>                              ^~~~
>                              stat)c_cast<char>(
> 1 error generated.
>

I don't see this problem with clang-2.8.

Why clang-3 does not allow code like (I don't have clang-3 to check)?

  int main()
  {
      unsigned char uc = 10;
      char c[2] = { uc , 1 };
  }

Is this really error, why the compiler does not cast?

> ...
> The same error appears several times then
>

Is this the same error all over?

Can you send me the list of such locations or a patch so I'll
be able to commit it to trunk and ask permissions to merge to release
branch.

Artyom

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

Re: [1.48.0] Beta 1 release candidates available

Lars Viklund
In reply to this post by Stephan T. Lavavej-2
On Wed, Oct 26, 2011 at 10:02:08PM +0000, Stephan T. Lavavej wrote:

> [Lars Viklund]
> > The problem is that this memory needs to be allocated up-front. All this
> > message means is exactly what it says - the default amount is not
> > sufficient and you need to change it in the build settings for the
> > source file that builds your PCH, adding /Zm123 to the advanced compiler
> > settings field there, or globally for your project.
>
> [Olaf van der Spek]
> > Hmm, right. Maybe it's time for MS to increase the default. :p
>
> The default is 75 MB on x86 (and 750 MB on x64), which is a fair amount of memory.  Including all STL headers in VC10 SP1 consumed only 29.3 MB when I last measured it.
>
> This has been increased to 83 MB in VC11 as of right now.

In one of the projects I'm working on, /Zm is at a comfortable 350 MB.

This of course is mostly due to putting any stable third party library
used in the PCH, which while nice from a compile-time cost perspective,
makes IntelliSense keel over and die.

--
Lars Viklund | [hidden email]

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

Re: [1.48.0] Beta 1 release candidates available

Beman Dawes
In reply to this post by Владислав Щапов
On Wed, Oct 26, 2011 at 1:04 PM, Владислав Щапов <[hidden email]> wrote:
> Hello!
>
> In the version 1.48.0beta1 there was a bug which leads to impossibility to
> use at least boost.asio and boost.unordered. Bugreport:
> https://svn.boost.org/trac/boost/ticket/6062

Looks like Daniel is on top of that one.

>
> And, please, fix a bug of Intel C++ and MSVC2010:
> https://svn.boost.org/trac/boost/ticket/5984

That's in Marcin Kalicinski's lap.

Neither of these are showstoppers for the beta.

Thanks for the reports!

--Beman

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