1.49.0 Beta 1 Release Candidate
Hi, I'm starting a build (using the Debian package configuration) and noticed several known bugs still present: These two bugs are patched on the trunk but not release. Can these be moved over, please? https://svn.boost.org/trac/boost/ticket/4657 https://svn.boost.org/trac/boost/ticket/6338 This issue has a simple patch that works around the problem for gcc versions prior to 4.6.3: https://svn.boost.org/trac/boost/ticket/5538 This issue has a patch that works (is used in Debian), though a jam expert could likely find a better fix: https://svn.boost.org/trac/boost/ticket/6286 Regards, -Steve (Boost maintainer for Debian)
On 1/28/2012 8:20 PM, Steve M. Robbins wrote:
Hi,
I'm starting a build (using the Debian package configuration) and noticed several known bugs still present:
These two bugs are patched on the trunk but not release. Can these be moved over, please?
https://svn.boost.org/trac/boost/ticket/4657 https://svn.boost.org/trac/boost/ticket/6338
This issue has a simple patch that works around the problem for gcc versions prior to 4.6.3:
https://svn.boost.org/trac/boost/ticket/5538
This issue has a patch that works (is used in Debian), though a jam expert could likely find a better fix:
You'll get more traction dealing with the maintainers of those libraries directly. The library maintainers are responsible for applying patches and merging the fixes to release, not the release managers. -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Sat, Jan 28, 2012 at 10:20:41PM -0600, Steve M. Robbins wrote:
Hi,
I'm starting a build (using the Debian package configuration) ...
So the build completed: "intrusive_ptr.hpp" caused my compiler to segfault. For Debian, we build all the boost libraries (Boost.Python and Python.MPI is built for each of several supported versions of python: 2.6, 2.7, and 3.2). This completed fine. Next, several of the tools are built: bbv2dir = $(CURDIR)/tools/build/v2 cd $(bbv2dir) && ./bootstrap.sh --with-toolset=gcc cd tools/bcp && $(JAM) cd tools/inspect/build && $(JAM) cd tools/quickbook && $(JAM) cd tools/wave/build && $(JAM) cd tools/regression/build && $(JAM) cd libs/python/pyste/install && python setup.py build The build failed during quickbook, with an Internal Compiler Error. I build with Debian's default gcc 4.6.2. The errors are below; can someone suggest a workaround? gcc.compile.c++ ../../bin.v2/tools/quickbook/src/gcc-4.6/release/debug-symbols-on/link-static/id_manager.o "g++" -ftemplate-depth-300 -O3 -finline-functions -Wno-inline -Wall -g -g0 -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"../.." -c -o "../../bin.v2/tools/quickbook/src/gcc-4.6/release/debug-symbols-on/link-static/id_manager.o" "src/id_manager.cpp" In file included from ../../boost/intrusive_ptr.hpp:16:0, from src/fwd.hpp:15, from src/values.hpp:20, from src/id_manager.hpp:14, from src/id_manager.cpp:9: ../../boost/smart_ptr/intrusive_ptr.hpp: In destructor 'boost::intrusive_ptr<T>::~intrusive_ptr() [with T = quickbook::file_info]': ../../boost/smart_ptr/intrusive_ptr.hpp:94:5: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. Preprocessed source stored into /tmp/cc9lzHW2.out file, please attach this to your bugreport. ...failed gcc.compile.c++ ../../bin.v2/tools/quickbook/src/gcc-4.6/release/debug-symbols-on/link-static/id_manager.o... gcc.compile.c++ ../../bin.v2/tools/quickbook/src/gcc-4.6/release/debug-symbols-on/link-static/phrase_element_grammar.o Thanks, -Steve
Hi, The following issue has a well-tested patch now on trunk. Can it be moved to release, please? https://svn.boost.org/trac/boost/ticket/4657 Thanks, -Steve
Hi, This issue is fixed on the trunk. Can it be pushed to release, please? https://svn.boost.org/trac/boost/ticket/6338 Thanks, -Steve
Hi, The following issue is fixed on trunk. Can it be moved to release, please? https://svn.boost.org/trac/boost/ticket/5538 Thanks, -Steve
On 1 Feb 2012, at 05:04, Steve M. Robbins wrote:
Hi,
The following issue is fixed on trunk. Can it be moved to release, please?
https://svn.boost.org/trac/boost/ticket/5538
Thanks, -Steve
Yes, I plan to do that after the release branch is open for modifications again, which is after the 1.49 release. Matthias
On Sat, Feb 04, 2012 at 09:04:38AM +0100, Matthias Troyer wrote:
The following issue is fixed on trunk. Can it be moved to release, please?
Yes, I plan to do that after the release branch is open for modifications again, which is after the 1.49 release.
My understanding is that the release branch is open to bug fixes at the moment. Is that wrong? Or does this not qualify? -S
Hi Steve, On Saturday, 4. February 2012 15:53:08 Steve M. Robbins wrote:
On Sat, Feb 04, 2012 at 09:04:38AM +0100, Matthias Troyer wrote:
The following issue is fixed on trunk. Can it be moved to release, please?
Yes, I plan to do that after the release branch is open for modifications again, which is after the 1.49 release.
My understanding is that the release branch is open to bug fixes at the moment. Is that wrong?
You have to ask the release managers for permission first. But the extended beta period was introduced in order to let ordinary Boost users discover such elementary bugs.
Or does this not qualify?
In my opinion, yes. Well tested and unfortunately not merged to release. Been there, forget that, too ;-)) 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
Jürgen Hunold wrote:
My understanding is that the release branch is open to bug fixes at the moment. Is that wrong?
You have to ask the release managers for permission first. But the extended beta period was introduced in order to let ordinary Boost users discover such elementary bugs.
The release branch is open until Monday, February 13th. For bug fixes, no permission is needed from a release manager in this period. (c.f. http://thread.gmane.org/gmane.comp.lib.boost.devel/227702/focus=227721 ) Regards, Michel
participants (5)
-
Eric Niebler -
Jürgen Hunold -
Matthias Troyer -
Michel Morin -
Steve M. Robbins