Re: [boost] [1.48.0] Release candidates available

Subject: Re: [boost] [1.48.0] Release candidates available
From: Ioannis Papadopoulos (ipapadop_at_[hidden])
Date: 2011-11-14 19:06:43

On 11/14/2011 09:47 AM, Beman Dawes wrote:
> Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
>
> md5sum on the originals:
>
> 7dd95e71c43ddd35997d9f2346e7f567 *boost_1_48_0.7z
> d1e9a7a7f532bb031a3c175d86688d95 *boost_1_48_0.tar.bz2
> 313a11e97eb56eb7efd18325354631be *boost_1_48_0.tar.gz
> b08fda829eec96b4f1071ce2ea6831f5 *boost_1_48_0.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.
>
> 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
>

Intel Core2 Quad with Fedora 13 x86-64
$ uname -a
Linux c0 2.6.34.9-69.fc13.x86_64 #1 SMP Tue May 3 09:23:03 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

Some warnings when compiling with gcc 4.6.1:

[Boost.Python]
libs/python/src/object/enum.cpp: In function ‘boost::python::api::object 
boost::python::objects::{anonymous}::new_enum_type(const char*, const 
char*)’:
libs/python/src/object/enum.cpp:150:11: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ 
bin.v2/libs/python/build/gcc-4.6.1/release/threading-multi/object/class.o
libs/python/src/object/class.cpp: In function ‘PyObject* 
boost::python::objects::static_data()’:
libs/python/src/object/class.cpp:211:11: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/class.cpp: In function 
‘boost::python::type_handle boost::python::objects::class_metatype()’:
libs/python/src/object/class.cpp:319:11: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/class.cpp: In function 
‘boost::python::type_handle boost::python::objects::class_type()’:
libs/python/src/object/class.cpp:473:11: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ 
bin.v2/libs/python/build/gcc-4.6.1/release/threading-multi/object/function.o
libs/python/src/object/function.cpp: In constructor 
‘boost::python::objects::function::function(const 
boost::python::objects::py_function&, const 
boost::python::detail::keyword*, unsigned int)’:
libs/python/src/object/function.cpp:108:9: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/function.cpp:110:9: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ 
bin.v2/libs/python/build/gcc-4.6.1/release/threading-multi/object/inheritance.o
gcc.compile.c++ 
bin.v2/libs/python/build/gcc-4.6.1/release/threading-multi/object/life_support.o
libs/python/src/object/life_support.cpp: In function ‘PyObject* 
boost::python::objects::make_nurse_and_patient(PyObject*, PyObject*)’:
libs/python/src/object/life_support.cpp:94:9: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/life_support.cpp:96:9: warning: dereferencing 
type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]

[Boost.Serialization]
gcc.compile.c++ 
bin.v2/libs/serialization/build/gcc-4.6.1/release/threading-multi/basic_iarchive.o
libs/serialization/src/basic_iarchive.cpp: In member function ‘const 
boost::archive::detail::basic_pointer_iserializer* 
boost::archive::detail::basic_iarchive_impl::load_pointer(boost::archive::detail::basic_iarchive&, 
void*&, const boost::archive::detail::basic_pointer_iserializer*, const 
boost::archive::detail::basic_pointer_iserializer* (*)(const 
boost::serialization::extended_type_info&))’:
libs/serialization/src/basic_iarchive.cpp:437:23: warning: variable 
‘new_cid’ set but not used [-Wunused-but-set-variable]
libs/serialization/src/basic_serializer_map.cpp: In member function 
‘bool boost::archive::detail::basic_serializer_map::insert(const 
boost::archive::detail::basic_serializer*)’:
libs/serialization/src/basic_serializer_map.cpp:46:47: warning: variable 
‘result’ set but not used [-Wunused-but-set-variable]

[Boost.Chrono]
gcc.compile.c++ 
bin.v2/libs/chrono/build/gcc-4.6.1/release/threading-multi/process_cpu_clocks.o
In file included from 
./boost/chrono/detail/inlined/process_cpu_clocks.hpp:39:0,
                  from libs/chrono/src/process_cpu_clocks.cpp:17:
./boost/chrono/detail/inlined/posix/process_cpu_clocks.hpp: In static 
member function ‘static 
boost::chrono::process_system_cpu_clock::time_point 
boost::chrono::process_system_cpu_clock::now()’:
./boost/chrono/detail/inlined/posix/process_cpu_clocks.hpp:218:1: 
warning: control reaches end of non-void function [-Wreturn-type]

A lot of warnings/remarks when compiling with Intel 12.20111011 (the 
output is in http://dl.dropbox.com/u/113056/icc_20111011.txt ):
[Boost.Xpressive]
[Boost.Proto]
[Boost.ICU]
[Boost.ProgramOptions]
[Boost.Serialization]
[Boost.SmartPointers]
[Boost.MPL]
[Boost.Iterator]
and others.

All warnings seem to be trivially fixable and I believe that they are 
valid.