[1.50.0] Release candidates available for testing
Release candidate files for 1.50.0 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, --Beman --PS: I tested the 7z version, and it built without errors on Win7/VC++ Express 2010 sp1
On 24 June 2012 14:02, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.50.0 are available at http://boost.cowic.de/rc/
I've uploaded the documentation to: http://www.boost.org/doc/libs/1_50_0/
On Sun, Jun 24, 2012 at 3:02 PM, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.50.0 are available at http://boost.cowic.de/rc/
What's the difference between http://boost.cowic.de/rc/boost-posix-2012-06-23.tar.bz2 and http://boost.cowic.de/rc/boost_1_50_0.tar.bz2? Olaf
On 24 June 2012 15:43, Olaf van der Spek <ml@vdspek.org> wrote:
On Sun, Jun 24, 2012 at 3:02 PM, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.50.0 are available at http://boost.cowic.de/rc/
What's the difference between http://boost.cowic.de/rc/boost-posix-2012-06-23.tar.bz2 and
That's the nightly release snapshot, it's generated every night by a cron job.
That's the 1.50 release candidate. I think Beman runs his release script manually for the release.
--layout=versioned seems to be broken: ~/projects/boost_1_50_0 $ ./bootstrap.sh && ./b2 --layout=versioned Building Boost.Build engine with toolset gcc... tools/build/v2/engine/bin.linuxx86_64/b2 Detecting Python version... 2.7 Detecting Python root... /usr Unicode/ICU support for Boost.Regex?... /usr Generating Boost.Build configuration in project-config.jam... Bootstrapping is done. To build, run: ./b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: ./b2 --help - Getting started guide: http://www.boost.org/more/getting_started/unix-variants.html - Boost.Build documentation: http://www.boost.org/boost-build2/doc/html/index.html Building the Boost C++ Libraries. Performing configuration checks - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - iconv (libc) : yes - icu : 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. /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:1079: in virtual-target.register-actual-name from module virtual- target error: Duplicate name of actual target: <pstage/lib>libboost_regex-gcc47- mt.so error: previous virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } error: created from ./stage-unversioned error: another virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { symlink%symlink.ln-libboost_regex-gcc47- mt-1_50.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } } error: created from ./stage-unversioned error: added properties: none error: removed properties: none /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:490: in actualize-no-scanner from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:135: in object(file-target)@3495.actualize from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build-system.jam:749: in load from module build-system /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/modules.jam:283: in import from module modules /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /home/phil/projects/boost_1_50_0/boost-build.jam:17: in module scope from module
Hi, I've managed to reproduce this on Ubuntu 11.10 but not on OS X 10.6.8 by following the steps described by Carl below. Kind regards, Jeroen Habraken On 25 June 2012 18:10, Carl Philipp Reh <sefi@s-e-f-i.de> wrote:
--layout=versioned seems to be broken:
~/projects/boost_1_50_0 $ ./bootstrap.sh && ./b2 --layout=versioned Building Boost.Build engine with toolset gcc... tools/build/v2/engine/bin.linuxx86_64/b2 Detecting Python version... 2.7 Detecting Python root... /usr Unicode/ICU support for Boost.Regex?... /usr Generating Boost.Build configuration in project-config.jam...
Bootstrapping is done. To build, run:
./b2
To adjust configuration, edit 'project-config.jam'. Further information:
- Command line help: ./b2 --help
- Getting started guide: http://www.boost.org/more/getting_started/unix-variants.html
- Boost.Build documentation: http://www.boost.org/boost-build2/doc/html/index.html
Building the Boost C++ Libraries.
Performing configuration checks
- has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - iconv (libc) : yes - icu : 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. /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:1079: in virtual-target.register-actual-name from module virtual- target error: Duplicate name of actual target: <pstage/lib>libboost_regex-gcc47- mt.so error: previous virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } error: created from ./stage-unversioned error: another virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { symlink%symlink.ln-libboost_regex-gcc47- mt-1_50.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } } error: created from ./stage-unversioned error: added properties: none error: removed properties: none /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:490: in actualize-no-scanner from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:135: in object(file-target)@3495.actualize from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build-system.jam:749: in load from module build-system /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/modules.jam:283: in import from module modules /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /home/phil/projects/boost_1_50_0/boost-build.jam:17: in module scope from module
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Mon, Jun 25, 2012 at 04:43:51PM +0200, Jeroen Habraken wrote:
Hi,
I've managed to reproduce this on Ubuntu 11.10 but not on OS X 10.6.8 by following the steps described by Carl below.
toolset darwin on OSX 1.7.4 is fine. toolsets gcc, pathscale, intel exhibit the problem on Ubuntu 10.04. toolset pgi doesn't exhibit the problem, probably due to the lack of compiler tag in the library names.
On 25 June 2012 18:10, Carl Philipp Reh <sefi@s-e-f-i.de> wrote:
--layout=versioned seems to be broken:
~/projects/boost_1_50_0 $ ./bootstrap.sh && ./b2 --layout=versioned Building Boost.Build engine with toolset gcc... tools/build/v2/engine/bin.linuxx86_64/b2 Detecting Python version... 2.7 Detecting Python root... /usr Unicode/ICU support for Boost.Regex?... /usr Generating Boost.Build configuration in project-config.jam...
Bootstrapping is done. To build, run:
./b2
To adjust configuration, edit 'project-config.jam'. Further information:
- Command line help: ./b2 --help
- Getting started guide: http://www.boost.org/more/getting_started/unix-variants.html
- Boost.Build documentation: http://www.boost.org/boost-build2/doc/html/index.html
Building the Boost C++ Libraries.
Performing configuration checks
- has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - iconv (libc) : yes - icu : 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. /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:1079: in virtual-target.register-actual-name from module virtual- target error: Duplicate name of actual target: <pstage/lib>libboost_regex-gcc47- mt.so error: previous virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } error: created from ./stage-unversioned error: another virtual target { symlink%symlink.ln-libboost_regex-gcc47- mt.so.SHARED_LIB { symlink%symlink.ln-libboost_regex-gcc47- mt-1_50.so.SHARED_LIB { common%common.copy-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.link.dll-libboost_regex-gcc47- mt-1_50.so.1.50.0.SHARED_LIB { gcc%gcc.compile.c++-c_regex_traits.o.OBJ { ../src/c_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++- cpp_regex_traits.o.OBJ { ../src/cpp_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-cregex.o.OBJ { ../src/cregex.cpp.CPP } } { gcc%gcc.compile.c++-fileiter.o.OBJ { ../src/fileiter.cpp.CPP } } { gcc%gcc.compile.c++-icu.o.OBJ { ../src/icu.cpp.CPP } } { gcc%gcc.compile.c++-instances.o.OBJ { ../src/instances.cpp.CPP } } { gcc%gcc.compile.c++-posix_api.o.OBJ { ../src/posix_api.cpp.CPP } } { gcc%gcc.compile.c++-regex.o.OBJ { ../src/regex.cpp.CPP } } { gcc%gcc.compile.c++-regex_debug.o.OBJ { ../src/regex_debug.cpp.CPP } } { gcc%gcc.compile.c++-regex_raw_buffer.o.OBJ { ../src/regex_raw_buffer.cpp.CPP } } { gcc%gcc.compile.c++-regex_traits_defaults.o.OBJ { ../src/regex_traits_defaults.cpp.CPP } } { gcc%gcc.compile.c++- static_mutex.o.OBJ { ../src/static_mutex.cpp.CPP } } { gcc%gcc.compile.c++- w32_regex_traits.o.OBJ { ../src/w32_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wc_regex_traits.o.OBJ { ../src/wc_regex_traits.cpp.CPP } } { gcc%gcc.compile.c++-wide_posix_api.o.OBJ { ../src/wide_posix_api.cpp.CPP } } { gcc%gcc.compile.c++-winstances.o.OBJ { ../src/winstances.cpp.CPP } } { gcc%gcc.compile.c++-usinstances.o.OBJ { ../src/usinstances.cpp.CPP } } } } } } error: created from ./stage-unversioned error: added properties: none error: removed properties: none /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:490: in actualize-no-scanner from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build/virtual- target.jam:135: in object(file-target)@3495.actualize from module object(file-target)@3495 /home/phil/projects/boost_1_50_0/tools/build/v2/build-system.jam:749: in load from module build-system /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/modules.jam:283: in import from module modules /home/phil/projects/boost_1_50_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /home/phil/projects/boost_1_50_0/boost-build.jam:17: in module scope from module
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost -- Lars Viklund | zao@acc.umu.se
Good builds on Windows 7 - 32 Bit VC8 - 32 & 64 VC9 - 32 & 64 VC10- 32 & 64 Libraries were (briefly) tested on and link/execute on 32 & 64 bit projects. On the other hand, my resulting binaries were two times larger than even the 1.50 beta build. 32-bit binaries went from 4.5GB to 9GB, 64-bit binaries went from 6GB to 12GB. Previously (for the 1.50 beta) the build only copied the libraries such as "libboost_libraryname-vcXX-opts-1_50.lib" to the stage directory, now it copies that plus the (identical) copy without the "1_50" in the name, doubling the size. Is this some build option that had its default changed? Tom On Sun, Jun 24, 2012 at 9:02 AM, Beman Dawes <bdawes@acm.org> wrote:
Release candidate files for 1.50.0 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,
--Beman
--PS: I tested the 7z version, and it built without errors on Win7/VC++ Express 2010 sp1
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi.
Good builds on Windows 7 - 32 Bit VC8 - 32 & 64 VC9 - 32 & 64 VC10- 32 & 64
Libraries were (briefly) tested on and link/execute on 32 & 64 bit projects.
On the other hand, my resulting binaries were two times larger than even the 1.50 beta build. 32-bit binaries went from 4.5GB to 9GB, 64-bit binaries went from 6GB to 12GB.
Previously (for the 1.50 beta) the build only copied the libraries such as "libboost_libraryname-vcXX-opts-1_50.lib" to the stage directory, now it copies that plus the (identical) copy without the "1_50" in the name, doubling the size. Is this some build option that had its default changed?
Yes, there was a fix related to this in boostcpp.jam (revision. I think that was the intended behaviour all along (to have both versioned and unversioned library variants built when the --layout=versioned is requested) but there were some typos in code that were silently causing the unversioned variants not to be built as expected. Ticket: https://svn.boost.org/trac/boost/ticket/6027 Commits: https://svn.boost.org/trac/boost/changeset/78937 https://svn.boost.org/trac/boost/changeset/78938 If this is something that should no be done - it is easy to disable again, but I guess thats for the release manager to say - what he wants the Boost library build to do. Hope this helps. Best regards, Jurko Gospodnetić
On 26 June 2012 11:19, Jurko Gospodnetić <jurko.gospodnetic@pke.hr> wrote:
I think that was the intended behaviour all along (to have both versioned and unversioned library variants built when the --layout=versioned is requested) but there were some typos in code that were silently causing the unversioned variants not to be built as expected.
I don't know enough about this to say if this is the case here, but non-trivial fixes for long standing bugs aren't really appropriate for the beta period. Particularly if they change behaviour.
Commits: https://svn.boost.org/trac/boost/changeset/78937 https://svn.boost.org/trac/boost/changeset/78938
More changes than those were merged to release: https://svn.boost.org/trac/boost/changeset/78941 Mostly whitespace changes? But the changes to 'make-unversioned-links' look significant.
Hi.
I don't know enough about this to say if this is the case here, but non-trivial fixes for long standing bugs aren't really appropriate for the beta period. Particularly if they change behaviour.
I believe the release branch was open for bug fixes at the time. Also, I reported the patch to the newsgroup - both boost.devel & boost.build (see thread 'Re: [boost-build] linking against pre-built libraries'). On the other hand - the patch is stand-alone and already stored on the trunk so it is easy enough to revert if the release manager deems it inappropriate.
Commits: https://svn.boost.org/trac/boost/changeset/78937 https://svn.boost.org/trac/boost/changeset/78938
More changes than those were merged to release:
Yup, sorry for not listing them all here, but the rest are stylistic changes/refactoring, added checking or changes to code that was not getting run at all and brought the release branch version up to date with the one on the trunk. Here's the exact list of equivalent trunk commits: https://svn.boost.org/trac/boost/changeset/78934 https://svn.boost.org/trac/boost/changeset/78935 https://svn.boost.org/trac/boost/changeset/78936 https://svn.boost.org/trac/boost/changeset/78937 https://svn.boost.org/trac/boost/changeset/78938 https://svn.boost.org/trac/boost/changeset/78939 I now updated the comment for the release branch revision [78941] to include the exact list of corresponding trunk branch revisions and their descriptions.
Mostly whitespace changes? But the changes to 'make-unversioned-links' look significant.
The change you are referring to comes from revision [78939] and is a simple refactoring without any behavioural change (just removed some duplicated crud). Also, the code in question was not getting run at all before commit 78938 due to the syntax error that was preventing the unversioned links from being created. Hope this helps. Best regards, Jurko Gospodnetić
On Tue, Jun 26, 2012 at 7:34 AM, Jurko Gospodnetić <jurko.gospodnetic@pke.hr> wrote:
Hi.
I don't know enough about this to say if this is the case here, but non-trivial fixes for long standing bugs aren't really appropriate for the beta period. Particularly if they change behaviour.
I believe the release branch was open for bug fixes at the time.
Boost infrastructure like Boost.Build needs special care because a problem can be so serious. Please revert these changes until after the release. Are these changes the source of the build errors reported by Carl Philipp Reh earlier in this thread? Or is that a separate problem? Thanks, --Beman
Hi.
Please revert these changes until after the release.
The change has been reverted. Non-versioned library variants no longer get built when the versioned library layout is requested on Windows & *nix and the original syntax errors are back in the code base.
Are these changes the source of the build errors reported by Carl Philipp Reh earlier in this thread?
Or is that a separate problem?
I do not know but should be easy enough for him to determine by rerunning the build based on the current release branch HEAD. Hope this helps. Best regards, Jurko Gospodnetić
Jurko Gospodnetić wrote:
Hi.
Please revert these changes until after the release.
The change has been reverted. Non-versioned library variants no longer get built when the versioned library layout is requested on Windows & *nix and the original syntax errors are back in the code base.
Are these changes the source of the build errors reported by Carl Philipp Reh earlier in this thread?
Or is that a separate problem?
I do not know but should be easy enough for him to determine by rerunning the build based on the current release branch HEAD.
Hope this helps.
Best regards, Jurko Gospodnetić
The --layout=versioned issue is gone on the current release branch HEAD. Can we expect another RC?
On Tue, Jun 26, 2012 at 05:21:10PM -0400, Beman Dawes wrote:
On Tue, Jun 26, 2012 at 12:23 PM, Carl Philipp Reh <sefi@s-e-f-i.de> wrote:
The --layout=versioned issue is gone on the current release branch HEAD. Can we expect another RC?
Yes.
Can I be pedantic and ask for the RCs to be numbered or otherwise labelled. It's very unfortunate to find something plainly named boost_1_50_0.tar.bz2 in the download folder a few weeks/months/years down the line and think that it's an official release, while it in fact may be a rather broken release candidate. -- Lars Viklund | zao@acc.umu.se
Hi.
Boost infrastructure like Boost.Build needs special care because a problem can be so serious.
Please revert these changes until after the release.
Now that the 1.50 release is out, I've merged the boostcpp.jam changes back into the release branch - so all the stylistic changes and minor tweaks are back in. The problematic 'unversioned library staging with --layout=versioned' code has been cleanly commented out so the behaviour is still the same as before. I tested the Boost library build and it worked fine on my computer (Windows 7, release branch, msvc 9.0). So if anyone wants the unversioned library targets enabled (personally, I do not need them and so do not have an itch to scratch here...) - he'll have to reenable the commented-out code and fix the duplicate target bug. But at least the release branch and the trunk are in sync again. Hope this helps. Best regards, Jurko Gospodnetić
participants (8)
-
Beman Dawes -
Carl Philipp Reh -
Daniel James -
Jeroen Habraken -
Jurko Gospodnetić -
Lars Viklund -
Olaf van der Spek -
Tom Kent