[1.48.0] Release candidates available
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
On 14 November 2011 16:47, Beman Dawes <bdawes@acm.org> 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
It compiles fine using both Apple's clang (Apple clang version 1.7 (tags/Apple/clang-77) (based on LLVM 2.9svn)) and GCC (i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)) on OS X 10.6.8. Jeroen
On Nov 14, 2011, at 7: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.
Downloaded, successfully extracted, and built successfully on Mac OS X (10.7.2) using both gcc 4.2.1 and clang [Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)] -- Marshall
Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
d1e9a7a7f532bb031a3c175d86688d95 *boost_1_48_0.tar.bz2
Downloaded, extracted, and built with g++ 4.5.1, Intel icpc 10.1.20081024, icpc 11.1.20100806, and icpc 12.1.20101006 on x86_64 Ubuntu Lucid. All but Intel icpc 10.1 build successfully. On that icpc 10.1 build I see several errors like
intel-linux.compile.c++ bin.v2/libs/python/build/intel-linux/release/link-static/threading-multi/object/function_doc_signature.o ./boost/cstdint.hpp(472): catastrophic error: #error directive: defaults not correct; you must hand modify boost/cstdint.hpp # error defaults not correct; you must hand modify boost/cstdint.hpp
compilation aborted for libs/python/src/object/function_doc_signature.cpp (code 4)
which I can neither confirm/deny are specific to my environment as icpc 10.1 doesn't appear at http://www.boost.org/development/tests/release/developer/summary.html. I do not know if this is a regression relative to earlier versions. - Rhys
Hi Beman, On Monday, 14. November 2011 16:47:13 Beman Dawes 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.
Succesfully built boost_1_48_0.7z on Windows Server 2008 using - msvc-9.0 - msvc-10.0 - mingw64-32 (gcc version 4.6.3 20111027 (prerelease) (GCC)) Yours, Jürgen -- Dipl.-Math. Jürgen Hunold | IVE mbH Software-Entwickler | Lützerodestraße 10 Tel: +49 511 897668 33 | 30161 Hannover, Germany Fax: +49 511 897668 29 | http://www.ivembh.de juergen.hunold@ivembh.de | | Geschäftsführer: Sitz des Unternehmens: Hannover | Univ.-Prof. Dr.-Ing. Thomas Siefer Amtsgericht Hannover, HRB 56965 | PD Dr.-Ing. Alfons Radtke
On Mon, Nov 14, 2011 at 10:47 AM, Beman Dawes <bdawes@acm.org> 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.
Succesfully built boost_1_48_0.7z on Windows 7 using VC++ 10 express. --Beman
On Monday, 14 November 2011, Beman Dawes wrote:
Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
It's on the beta site as well now. My internet connection is very spotty, so I might be a bit slow updating the site for the release.
On Mon, 2011-11-14 at 17:47 +0200, Beman Dawes wrote:
Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
Successfull build on x86_64 RHEL6 Linux with g++ 4.4.5 Successfull build on x86_64 RHEL5 Linux with g++ 4.1.2 Successfull build on i686 CentOS 4.9 Linux with g++ 3.4.6 We build RPM-packages for each system using this set of options: ./bjam --disable-filesystem2 -a --layout=system install link=static variant=release threading=multi cxxflags=-fPIC Mika Heiskanen
On 14 November 2011 09:47, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
7dd95e71c43ddd35997d9f2346e7f567 *boost_1_48_0.7z
Successfull build (almost) with: MSVC 8, stlport 5.1, x64 | x86, on Windows XP 64. b2 variant=release link=static threading=multi runtime-link=shared stdlib=stlport -j4 address-model=32 stage Wave fails due to probably missing #include that old stlport dislikes (vector<T> doesn't allow T to be non complete). No biggie I guess. I don't remember what -j4 means, but it's in our build script so I left it at that.. - Christian
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.
On Monday, November 14, 2011 11:47 PM, 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.
There were a couple of errors in signals when building with gcc-4.6.1 on ubuntu x64 with std=c++0x: gcc.compile.c++ bin.v2/libs/signals/build/gcc-4.6.1/release/threading-multi/named_slot_map.o libs/signals/src/named_slot_map.cpp: In member function ‘void boost::signals::detail::named_slot_map::disconnect(const boost::signals::detail::stored_group&)’: libs/signals/src/named_slot_map.cpp:105:23: error: call of overloaded ‘erase(boost::signals::detail::named_slot_map::group_iterator&)’ is ambiguous libs/signals/src/named_slot_map.cpp:105:23: note: candidates are: /usr/include/c++/4.6/bits/stl_map.h:613:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare, _Alloc>::erase(std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::iterator = std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator = std::_Rb_tree_const_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >] /usr/include/c++/4.6/bits/stl_map.h:643:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::size_type std::map<_Key, _Tp, _Compare, _Alloc>::erase(const key_type&) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::size_type = long unsigned int, std::map<_Key, _Tp, _Compare, _Alloc>::key_type = boost::signals::detail::stored_group] libs/signals/src/named_slot_map.cpp: In member function ‘void boost::signals::detail::named_slot_map::remove_disconnected_slots()’: libs/signals/src/named_slot_map.cpp:128:35: error: call of overloaded ‘erase(std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >::_Self)’ is ambiguous libs/signals/src/named_slot_map.cpp:128:35: note: candidates are: /usr/include/c++/4.6/bits/stl_map.h:613:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare, _Alloc>::erase(std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::iterator = std::_Rb_tree_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::const_iterator = std::_Rb_tree_const_iterator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >] /usr/include/c++/4.6/bits/stl_map.h:643:7: note: std::map<_Key, _Tp, _Compare, _Alloc>::size_type std::map<_Key, _Tp, _Compare, _Alloc>::erase(const key_type&) [with _Key = boost::signals::detail::stored_group, _Tp = std::list<boost::signals::detail::connection_slot_pair>, _Compare = boost::function2<bool, boost::signals::detail::stored_group, boost::signals::detail::stored_group>, _Alloc = std::allocator<std::pair<const boost::signals::detail::stored_group, std::list<boost::signals::detail::connection_slot_pair> > >, std::map<_Key, _Tp, _Compare, _Alloc>::size_type = long unsigned int, std::map<_Key, _Tp, _Compare, _Alloc>::key_type = boost::signals::detail::stored_group] "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1 -DBOOST_SIGNALS_DYN_LINK=1 -DBOOST_SIGNALS_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/signals/build/gcc-4.6.1/release/threading-multi/named_slot_map.o" "libs/signals/src/named_slot_map.cpp" ...failed gcc.compile.c++ bin.v2/libs/signals/build/gcc-4.6.1/release/threading-multi/named_slot_map.o... Ben
On Tuesday, November 15, 2011 11:18 AM, Ben Pope wrote:
On Monday, November 14, 2011 11:47 PM, 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.
There were a couple of errors in signals when building with gcc-4.6.1 on ubuntu x64 with std=c++0x:
Same with clang version 3.0 (tags/RELEASE_30/rc3 144380) and std=c++0x (but obviously easier to read): Although, looking at it, I wonder if I'm using the correct STL for clang. compile.c++.without-pth bin.v2/libs/signals/build/clang-linux-linux/release/threading-multi/named_slot_map.o libs/signals/src/named_slot_map.cpp:105:12: error: call to member function 'erase' is ambiguous groups.erase(group); ~~~~~~~^~~~~ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:613:7: note: candidate function erase(const_iterator __position) ^ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:643:7: note: candidate function erase(const key_type& __x) ^ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:662:7: note: candidate function not viable: requires 2 arguments, but 1 was provided erase(const_iterator __first, const_iterator __last) ^ libs/signals/src/named_slot_map.cpp:128:26: error: call to member function 'erase' is ambiguous if (empty(g)) groups.erase(g++); ~~~~~~~^~~~~ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:613:7: note: candidate function erase(const_iterator __position) ^ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:643:7: note: candidate function erase(const key_type& __x) ^ /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/stl_map.h:662:7: note: candidate function not viable: requires 2 arguments, but 1 was provided erase(const_iterator __first, const_iterator __last) ^ 2 errors generated. "clang++" -c -x c++ -std=c++0x -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1 -DBOOST_SIGNALS_DYN_LINK=1 -DBOOST_SIGNALS_NO_LIB=1 -DNDEBUG -I"." -o "bin.v2/libs/signals/build/clang-linux-linux/release/threading-multi/named_slot_map.o" "libs/signals/src/named_slot_map.cpp" ...failed compile.c++.without-pth bin.v2/libs/signals/build/clang-linux-linux/release/threading-multi/named_slot_map.o... Ben
On Tuesday, November 15, 2011 11:18 AM, Ben Pope wrote:
There were a couple of errors in signals when building with gcc-4.6.1 on ubuntu x64 with std=c++0x:
Ben, could you file a bug? This isn't going to hold up 1.38, but it would be nice to have this addressed in a future release. Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Tuesday, November 15, 2011 01:44 PM, Eric Niebler wrote:
On Tuesday, November 15, 2011 11:18 AM, Ben Pope wrote:
There were a couple of errors in signals when building with gcc-4.6.1 on ubuntu x64 with std=c++0x: Ben, could you file a bug? This isn't going to hold up 1.38, but it would be nice to have this addressed in a future release.
Thanks,
Tickets #5774, #4999 already mention this Ben
Release candidate files for 1.48.0 are available at http://boost.cowic.de/rc/
minor error while installing: a wrong toolset gives outdated error message: $ ./bootstrap.sh --with-toolset=WrongToolSet Building Boost.Build engine with toolset WrongToolSet... Failed to build Boost.Build build engine Consult 'bootstrap.log' for more details Content of bootstrap.log: ### ### Unknown toolset: WrongToolSet ### ### You can specify the toolset as the argument, i.e.: ### ./build.sh gcc ### ### Toolsets supported by this script are: ### acc, como, darwin, gcc, intel-darwin, intel-linux, kcc, kylix, ### mipspro, mingw(msys), pathscale, pgi, qcc, sun, sunpro, tru64cxx, vacpp ... The message should say: ### ./bootstrap.sh --with-toolset=gcc Frédéric
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
Compiles fine on xlC 11.1 on a Power5+ with warnings, the output is in: http://dl.dropbox.com/u/113056/xlC11.1.txt
On Mon, Nov 14, 2011 at 10:47 AM, Beman Dawes <bdawes@acm.org> 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
Thanks to all who posted responses. The files have been uploaded to SourceForge and a release notice should go out later this evening. --Beman
participants (13)
-
Beman Dawes -
Ben Pope -
Christian Holmquist -
Daniel James -
Eric Niebler -
Frédéric Bron -
Ioannis Papadopoulos -
Jeroen Habraken -
Jürgen Hunold -
KTC -
Marshall Clow -
Mika Heiskanen -
Rhys Ulerich