[1.45.0] Release candidates available
See http://boost.cowic.de/rc/ Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge. Thanks, --Beman
On Nov 17, 2010, at 9:49 AM, Beman Dawes wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Compiled w/o error here (a couple dozen warnings, none new) Mac OS X 10.6.4, gcc 4.2.1, toolset=darwin -- Marshall
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 6:49 PM Subject: [boost] [1.45.0] Release candidates available
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Hi, I know that this is an old toolset, but I use it to check with an old gcc compiler. cygwin-1.5 gcc-3.4 ============= There is a bjam ERROR and it stops.
cd /boost/v45 bjam
Building the Boost C++ Libraries. /boost/v45/tools/build/v2/build/configure.jam:145: in builds-raw *** argument error * rule UPDATE_NOW ( targets * : log ? : ignore-minus-n ? ) * called with: ( <pbin.v2/libs/regex/build/gcc-3.4.4/debug>has_icu.exe : : ignore-minus-n : ignore-minus-q ) * extra argument ignore-minus-q (builtin):see definition of rule 'UPDATE_NOW' being called /boost/v45/tools/build/v2/build/configure.jam:179: in configure.builds ... Best, Vicente
On 11/17/2010 2:03 PM, vicente.botet wrote:
----- Original Message ----- From: "Beman Dawes"<bdawes@acm.org> To: "Boost Developers List"<boost@lists.boost.org> Sent: Wednesday, November 17, 2010 6:49 PM Subject: [boost] [1.45.0] Release candidates available
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Hi,
I know that this is an old toolset, but I use it to check with an old gcc compiler.
cygwin-1.5 gcc-3.4 ============= There is a bjam ERROR and it stops.
cd /boost/v45 bjam
Did you build bjam from the sources included in the RC? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
http://viboes.blogspot.com/ ----- Original Message ----- From: "Rene Rivera" <grafikrobot@gmail.com> To: <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 9:24 PM Subject: Re: [boost] [1.45.0] Release candidates available
On 11/17/2010 2:03 PM, vicente.botet wrote:
----- Original Message ----- From: "Beman Dawes"<bdawes@acm.org> To: "Boost Developers List"<boost@lists.boost.org> Sent: Wednesday, November 17, 2010 6:49 PM Subject: [boost] [1.45.0] Release candidates available
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Hi,
I know that this is an old toolset, but I use it to check with an old gcc compiler.
cygwin-1.5 gcc-3.4 ============= There is a bjam ERROR and it stops.
cd /boost/v45 bjam
Did you build bjam from the sources included in the RC?
Non. I will try it. Do you mean that we need to update the bjam version when we update the Boost version? Is this written somewhere? Best, Vicente
vicente.botet wrote:
----- Original Message ----- From: "Rene Rivera" <grafikrobot@gmail.com> To: <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 9:24 PM Subject: Re: [boost] [1.45.0] Release candidates available
On 11/17/2010 2:03 PM, vicente.botet wrote:
----- Original Message ----- From: "Beman Dawes"<bdawes@acm.org> To: "Boost Developers List"<boost@lists.boost.org> Sent: Wednesday, November 17, 2010 6:49 PM Subject: [boost] [1.45.0] Release candidates available
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Hi,
I know that this is an old toolset, but I use it to check with an old gcc compiler.
cygwin-1.5 gcc-3.4 ============= There is a bjam ERROR and it stops.
cd /boost/v45 bjam
Did you build bjam from the sources included in the RC?
Non. I will try it. Do you mean that we need to update the bjam version when we update the Boost version? Is this written somewhere?
The official procedure to build each release is: ./bootstrap.sh ./bjam If you're using system-wide bjam, you should be prepared that eventually, it will cease to work. There will be better checking and reporting of required version in future. - Volodya
Vladimir Prus-3 wrote:
vicente.botet wrote:
On 11/17/2010 2:03 PM, vicente.botet wrote:
Do you mean that we need to update the bjam version when we update the Boost version? Is this written somewhere?
The official procedure to build each release is:
./bootstrap.sh ./bjam
If you're using system-wide bjam, you should be prepared that eventually, it will cease to work. There will be better checking and reporting of required version in future.
Thanks Volodya, I will use it next time. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/1-45-0-Release-candidates-available-tp304... Sent from the Boost - Dev mailing list archive at Nabble.com.
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 6:49 PM Subject: [boost] [1.45.0] Release candidates available
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
cygwin-1.7 gcc-4.3 ============= cd /boost/v45 bjam -j2 Everything is OK (except that I have not installed python and this is not recognized) Vicente P.S. Rene, I didn't need to build bjam for this platform. $ bjam --version Boost.Build V2 (Milestone 12) Boost.Jam 03.1.18 I had an older version with cygwin 1.5. $ bjam --version Boost.Build V2 (Milestone 12) Boost.Jam 03.1.17
Please download the file for your favorite platform, try a build, and let us know if it works OK.
bjam --built-type=complete --layout=versioned compiles cleanly on Intel's ICPC 11.1 20100806 on Ubuntu Lucid x86_64. - Rhys
On 17/11/2010 17:49, Beman Dawes wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
VC10 (with latest bzip2, zlib and ICU) build fine as expected for both x86 & x64. KTC
On Wed, Nov 17, 2010 at 12:49 PM, Beman Dawes <bdawes@acm.org> wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports! We look good to go, and plan to push the release out later today. --Beman
On Thu, Nov 18, 2010 at 1:34 PM, Beman Dawes <bdawes@acm.org> wrote:
On Wed, Nov 17, 2010 at 12:49 PM, Beman Dawes <bdawes@acm.org> wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports!
We look good to go, and plan to push the release out later today.
--Beman
a little late but FWIW it builds ok on: ubuntu 10.04 LTS 32bit + gcc 4.5.1 vista 32bit + msvc9 builds with a few errors (mainly in Boost.Thread) on vista 32bit + cygwin + gcc 4.5.1 the output of ./bjam -j 2 from all three runs can be found here: http://kifri.fri.uniza.sk/~chochlik/boost_1_45_0_rc_log/ BR, Matus
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports!
We look good to go, and plan to push the release out later today.
It's not a killer for the release (and my apologies for not looking at this earlier), but I'm unable to build the PDF's for this release, bjam fails with: error: Unable to find file or target named error: '../../../LICENSE_1_0.txt' error: referred from project at error: '../../tools/build/v2/engine/doc' I'll look into disabling Boost.Build's docs for now, John.
On Thu, Nov 18, 2010 at 1:24 PM, John Maddock <boost.regex@virgin.net> wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports!
We look good to go, and plan to push the release out later today.
It's not a killer for the release (and my apologies for not looking at this earlier), but I'm unable to build the PDF's for this release, bjam fails with:
error: Unable to find file or target named error: '../../../LICENSE_1_0.txt' error: referred from project at error: '../../tools/build/v2/engine/doc'
I'll look into disabling Boost.Build's docs for now,
I've created the 1.45.0 folder on SourceForge, but haven't uploaded files yet. I'll hold for couple of hours to see if you can find a fix. It would have to be very low risk, however. --Beman
On Thu, Nov 18, 2010 at 3:25 PM, Beman Dawes <bdawes@acm.org> wrote:
On Thu, Nov 18, 2010 at 1:24 PM, John Maddock <boost.regex@virgin.net> wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports!
We look good to go, and plan to push the release out later today.
It's not a killer for the release (and my apologies for not looking at this earlier), but I'm unable to build the PDF's for this release, bjam fails with:
error: Unable to find file or target named error: '../../../LICENSE_1_0.txt' error: referred from project at error: '../../tools/build/v2/engine/doc'
I'll look into disabling Boost.Build's docs for now,
I've created the 1.45.0 folder on SourceForge, but haven't uploaded files yet.
I'll hold for couple of hours to see if you can find a fix. It would have to be very low risk, however.
Nothing from John, so I'll continue with the release process. --Beman
Beman Dawes schrieb:
On Thu, Nov 18, 2010 at 3:25 PM, Beman Dawes <bdawes@acm.org> wrote:
On Thu, Nov 18, 2010 at 1:24 PM, John Maddock <boost.regex@virgin.net> wrote:
Please download the file for your favorite platform, try a build, and let us know if it works OK. We like some independent confirmation before pushing the files up to SourceForge.
Thanks for all the reports!
We look good to go, and plan to push the release out later today.
It's not a killer for the release (and my apologies for not looking at this earlier), but I'm unable to build the PDF's for this release, bjam fails with:
error: Unable to find file or target named error: '../../../LICENSE_1_0.txt' error: referred from project at error: '../../tools/build/v2/engine/doc'
I'll look into disabling Boost.Build's docs for now,
I've created the 1.45.0 folder on SourceForge, but haven't uploaded files yet.
I'll hold for couple of hours to see if you can find a fix. It would have to be very low risk, however.
Nothing from John, so I'll continue with the release process.
--Beman
We got an issue in Spirit. I am responsible for that. See these posts http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875 for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that. Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch? I apologize for the inconvenience. I am really sorry :( Best regards, Christopher
On 11/19/2010 3:36 AM, Christopher Schmidt wrote:
We got an issue in Spirit. I am responsible for that. See these posts
http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875
for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that.
Oh, it can get worse. :-) Honestly, I'm not of a mind to hold up the release for this. No existing code will be broken by this, is that correct? If only new functionality is broken, then folks can wait for a working version.
Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch?
That depends on whether Beman has rolled the release already and whether you have a doc patch ready to go.
I apologize for the inconvenience. I am really sorry :(
It happens. Too bad it wasn't spotted sooner. -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 11/19/2010 7:38 AM, Eric Niebler wrote:
On 11/19/2010 3:36 AM, Christopher Schmidt wrote:
We got an issue in Spirit. I am responsible for that. See these posts
http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875
for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that.
Oh, it can get worse. :-) Honestly, I'm not of a mind to hold up the release for this. No existing code will be broken by this, is that correct? If only new functionality is broken, then folks can wait for a working version.
I feel the same way.
Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch?
That depends on whether Beman has rolled the release already and whether you have a doc patch ready to go.
If Beman has rolled the release.. AN option would be to put something on the web site notes (and release posts). -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
On Fri, Nov 19, 2010 at 3:00 PM, Rene Rivera <grafikrobot@gmail.com> wrote:
On 11/19/2010 7:38 AM, Eric Niebler wrote:
On 11/19/2010 3:36 AM, Christopher Schmidt wrote:
We got an issue in Spirit. I am responsible for that. See these posts
http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875
for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that.
Oh, it can get worse. :-) Honestly, I'm not of a mind to hold up the release for this. No existing code will be broken by this, is that correct? If only new functionality is broken, then folks can wait for a working version.
I feel the same way.
Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch?
That depends on whether Beman has rolled the release already and whether you have a doc patch ready to go.
If Beman has rolled the release.. AN option would be to put something on the web site notes (and release posts).
What do you think about an "Known issues" section on the release notes?
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Mit freundlichen Grüßen, With best regards, Wolfgang Forstmeier Homines sumus nun dei (Petronius) ------------------------------------------- mailto:wolfgang.forstmeier@gmail.com
Rene Rivera schrieb:
On 11/19/2010 7:38 AM, Eric Niebler wrote:
On 11/19/2010 3:36 AM, Christopher Schmidt wrote:
We got an issue in Spirit. I am responsible for that. See these posts
http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875
for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that.
Oh, it can get worse. :-) Honestly, I'm not of a mind to hold up the release for this. No existing code will be broken by this, is that correct? If only new functionality is broken, then folks can wait for a working version.
I feel the same way.
Yeah, just code that uses a new fusion feature (adapted 'abstract data types') will be affected.
Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch?
That depends on whether Beman has rolled the release already and whether you have a doc patch ready to go.
If Beman has rolled the release.. AN option would be to put something on the web site notes (and release posts).
As the release is finally on its way I do not want to interrupt the process. I created a track ticket and attached the patch to it. https://svn.boost.org/trac/boost/ticket/4871 Version is set to Boost 1.46.0, Milestone is set to Boost 1.47.0. The compile errors are pretty much straightforward and I guess spirit users will search the trac tickets first. I am sorry for the inconveniences. Best regards, Christopher
I've created the 1.45.0 folder on SourceForge, but haven't uploaded files yet.
I'll hold for couple of hours to see if you can find a fix. It would have to be very low risk, however.
Nothing from John, so I'll continue with the release process.
Nod, it was taking so long to build all the PDF's that I needed to go off to bed! In any case as I said before, I'll patch my local copy to exclude Boost.Build from this set of PDF's, so *don't hold the release for this*. John.
participants (13)
-
Beman Dawes -
Christopher Schmidt -
Eric Niebler -
John Maddock -
KTC -
Marshall Clow -
Matus Chochlik -
Rene Rivera -
Rhys Ulerich -
viboes -
vicente.botet
-
Vladimir Prus -
Wolfgang Forstmeier