|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r50005 - in website/public_html/beta/feed: . downloads
From: grafikrobot_at_[hidden]
Date: 2008-11-29 00:16:56
Author: grafik
Date: 2008-11-29 00:16:55 EST (Sat, 29 Nov 2008)
New Revision: 50005
URL: http://svn.boost.org/trac/boost/changeset/50005
Log:
Boost Jam 3.1.17 release.
Text files modified:
website/public_html/beta/feed/downloads.rss | 188 +++++++++++++++++++++++----------------
website/public_html/beta/feed/downloads/bjam_3_1_17.qbk | 2
2 files changed, 113 insertions(+), 77 deletions(-)
Modified: website/public_html/beta/feed/downloads.rss
==============================================================================
--- website/public_html/beta/feed/downloads.rss (original)
+++ website/public_html/beta/feed/downloads.rss 2008-11-29 00:16:55 EST (Sat, 29 Nov 2008)
@@ -18,84 +18,118 @@
more readable!
</p>
<p>
- [list [li Reflect the results of calling bjam from Python. -- <em>Rene
- R.</em> ] [li For building on Windows: Rework how arguments are parsed
- and tested to fix handling of quoted arguments, options arguments, and arguments
- with &quot;=&quot;. -- <em>Rene R.</em> ] [li Try to work around
- at least one compiler bug with GCC and variable aliasing that causes crashes
- with hashing file cache entries. -- <em>Rene R.</em> ] [li Add -Wc,-fno-strict-aliasing
- for QCC/QNX to avoid the same aliasing crashes as in the general GCC 4.x series
- (thanks to Niklas Angare for the fix). -- <em>Rene R.</em> ] [li
- On Windows let the child bjam commands inherit stdin, as some commands assume
- it's available. -- <em>Rene R.</em> ] [li On Windows don't limit
- bjam output to ASCII as some tools output characters in extended character sets.
- -- <em>Rene R.</em> ] [li Isolate running of bjam tests to individual
- bjam instances to prevent possible spillover errors from one test affecting another
- test. Separate the bjam used to run the tests vs. the bjam being tested. And
- add automatic re-building of the bjam being tested. -- <em>Rene R.</em>
- ] [li Fix some possible overrun issues revealed by Fortify build. Thanks to Steven
- Robbins for pointing out the issues. -- <em>Rene R.</em> ] [li Handle
- \n and \r escape sequences. -- <em>Vladimir P.</em> ] [li Minor edits
- to remove -Wall warnings. -- <em>Rene R.</em> ] [li Dynamically adjust
- pwd buffer query size to allow for when PATH_MAX is default defined instead of
- being provided by the system C library. -- <em>Rene R.</em> ] [li
- Minor perf improvement for bjam by replacing hash function with faster version.
- Only 1% diff for Boost tree. -- <em>Rene R.</em> ] [li Updated Boost
- Jam's error location reporting when parsing Jamfiles. Now it reports the correct
- error location information when encountering an unexpected EOF. It now also reports
- where an invalid lexical token being read started instead of finished which makes
- it much easier to find errors like unclosed quotes or curly braces. -- <em>Jurko
- G.</em> ] [li Removed the -xarch=generic architecture from build.jam as
- this option is unknown so the Sun compilers on Linux. -- <em>Noel B.</em>
- ] [li Fixed a bug with T_FATE_ISTMP getting reported as T_FATE_ISTMP &amp; T_FATE_NEEDTMP
+ <ul><li>Reflect the results of calling bjam from Python. -- <em>Rene R.</em>
+ </li>
+ <li>For building on Windows: Rework how arguments are parsed and tested to fix handling
+ of quoted arguments, options arguments, and arguments with &quot;=&quot;. --
+ <em>Rene R.</em> </li>
+ <li>Try to work around at least one compiler bug with
+ GCC and variable aliasing that causes crashes with hashing file cache entries.
+ -- <em>Rene R.</em> </li>
+ <li>Add -Wc,-fno-strict-aliasing for QCC/QNX to avoid
+ the same aliasing crashes as in the general GCC 4.x series (thanks to Niklas
+ Angare for the fix). -- <em>Rene R.</em> </li>
+ <li>On Windows let the child
+ bjam commands inherit stdin, as some commands assume it's available. -- <em>Rene
+ R.</em> </li>
+ <li>On Windows don't limit bjam output to ASCII as some tools output
+ characters in extended character sets. -- <em>Rene R.</em> </li>
+ <li>Isolate
+ running of bjam tests to individual bjam instances to prevent possible spillover
+ errors from one test affecting another test. Separate the bjam used to run the
+ tests vs. the bjam being tested. And add automatic re-building of the bjam being
+ tested. -- <em>Rene R.</em> </li>
+ <li>Fix some possible overrun issues revealed
+ by Fortify build. Thanks to Steven Robbins for pointing out the issues. -- <em>Rene
+ R.</em> </li>
+ <li>Handle \n and \r escape sequences. -- <em>Vladimir P.</em>
+ </li>
+ <li>Minor edits to remove -Wall warnings. -- <em>Rene R.</em> </li>
+ <li>Dynamically
+ adjust pwd buffer query size to allow for when PATH_MAX is default defined instead
+ of being provided by the system C library. -- <em>Rene R.</em> </li>
+ <li>Minor
+ perf improvement for bjam by replacing hash function with faster version. Only
+ 1% diff for Boost tree. -- <em>Rene R.</em> </li>
+ <li>Updated Boost Jam's error
+ location reporting when parsing Jamfiles. Now it reports the correct error location
+ information when encountering an unexpected EOF. It now also reports where an
+ invalid lexical token being read started instead of finished which makes it much
+ easier to find errors like unclosed quotes or curly braces. -- <em>Jurko
+ G.</em> </li>
+ <li>Removed the -xarch=generic architecture from build.jam as this
+ option is unknown so the Sun compilers on Linux. -- <em>Noel B.</em>
+ </li>
+ <li>Fixed a bug with T_FATE_ISTMP getting reported as T_FATE_ISTMP &amp; T_FATE_NEEDTMP
at the same time due to a missing break in a switch statement. -- <em>Jurko
- G.</em> ] [li Fixed a Boost Jam bug causing it to sometimes trigger actions
- depending on targets that have not been built yet. -- <em>Jurko G.</em>
- ] [li Added missing documentation for Boost Jam's :T variable expansion modifier
- which converts all back-slashes ('\') to forward slashed ('/'). -- <em>Jurko
- G.</em> ] [li Added Boost Jam support for executing command lines longer
- than 2047 characters (up to 8191) characters when running on Windows XP or later
- OS version. -- <em>Jurko G.</em> ] [li Fixed a Boost Jam bug on Windows
- causing its SHELL command not to work correctly with some commands containing
- quotes. -- <em>Jurko G.</em> ] [li Corrected a potential memory leak
- in Boost Jam's builtin_shell() function that would appear should Boost Jam ever
- start to release its allocated string objects. -- <em>Jurko G.</em>
- ] [li Made all Boost Jam's ECHO commands automatically flush the standard output
- to make that output more promptly displayed to the user. -- <em>Jurko G.</em>
- ] [li Made Boost Jam tests quote their bjam executable name when calling it allowing
- those executables to contain spaces in their name and/or path. -- <em>Jurko
- G.</em> ] [li Change execunix.c to always use fork() instead of vfork()
- on the Mac. This works around known issues with bjam on PPC under Tiger and a
- problem reported by Rene with bjam on x86 under Leopard. -- <em>Noel B.</em>
- ] [li Corrected a bug in Boost Jam's base Jambase script causing it to trim the
- error message displayed when its boost-build rule gets called multiple times.
- -- <em>Jurko G.</em> ] [li When importing from Python into an module
- with empty string as name, import into root module. -- <em>Vladimir P.</em>
- ] [li Patch for the NORMALIZE_PATH builtin Boost Jam rule as well as an appropriate
- update for the path.jam Boost Build module where that rule was being used to
- implement path join and related operations. -- <em>Jurko G.</em>
- ] [li Fixed a bug causing Boost Jam not to handle target file names specified
- as both short and long file names correctly. -- <em>Jurko G.</em>
- ] [li Relaxed test, ignoring case of drive letter. -- <em>Roland S.</em>
- ] [li Implemented a patch contributed by Igor Nazarenko reimplementing the list_sort()
- function to use a C qsort() function instead of a hand-crafted merge-sort algorithm.
- Makes some list sortings (e.g. 1,2,1,2,1,2,1,2, ...) extremely faster, in turn
- significantly speeding up some project builds. -- <em>Jurko G.</em>
- ] [li Fixed a bug with bjam not handling the '' root Windows path correctly without
- its drive letter being specified. -- <em>Jurko G.</em> ] [li Solved
- the problem with child process returning the value 259 (Windows constant STILL_ACTIVE)
- causing bjam never to detect that it exited and therefore keep running in an
- endless loop. -- <em>Jurko G.</em> ] [li Solved the problem with
- bjam going into an active wait state, hogging up processor resources, when waiting
- for one of its child processes to terminate while not all of its available child
- process slots are being used. -- <em>Jurko G.</em> ] [li Solved a
- race condition between bjam's output reading/child process termination detection
- and the child process's output generation/termination which could have caused
- bjam not to collect the terminated process's final output. -- <em>Jurko
- G.</em> ] [li Change from vfork to fork for executing actions on Darwin
- to improve stability. -- <em>Noel B.</em> ] [li Code reformatting
- and cleanups. -- <em>Jurko G.</em> ] [li Implement ISFILE built-in.
- -- <em>Vladimir P.</em> ] ]
+ G.</em> </li>
+ <li>Fixed a Boost Jam bug causing it to sometimes trigger actions depending
+ on targets that have not been built yet. -- <em>Jurko G.</em> </li>
+ <li>Added
+ missing documentation for Boost Jam's :T variable expansion modifier which converts
+ all back-slashes ('\') to forward slashed ('/'). -- <em>Jurko G.</em>
+ </li>
+ <li>Added Boost Jam support for executing command lines longer than 2047 characters
+ (up to 8191) characters when running on Windows XP or later OS version. -- <em>Jurko
+ G.</em> </li>
+ <li>Fixed a Boost Jam bug on Windows causing its SHELL command not
+ to work correctly with some commands containing quotes. -- <em>Jurko G.</em>
+ </li>
+ <li>Corrected a potential memory leak in Boost Jam's builtin_shell() function that
+ would appear should Boost Jam ever start to release its allocated string objects.
+ -- <em>Jurko G.</em> </li>
+ <li>Made all Boost Jam's ECHO commands automatically
+ flush the standard output to make that output more promptly displayed to the
+ user. -- <em>Jurko G.</em> </li>
+ <li>Made Boost Jam tests quote their bjam
+ executable name when calling it allowing those executables to contain spaces
+ in their name and/or path. -- <em>Jurko G.</em> </li>
+ <li>Change execunix.c
+ to always use fork() instead of vfork() on the Mac. This works around known issues
+ with bjam on PPC under Tiger and a problem reported by Rene with bjam on x86
+ under Leopard. -- <em>Noel B.</em> </li>
+ <li>Corrected a bug in Boost Jam's
+ base Jambase script causing it to trim the error message displayed when its boost-build
+ rule gets called multiple times. -- <em>Jurko G.</em> </li>
+ <li>When importing
+ from Python into an module with empty string as name, import into root module.
+ -- <em>Vladimir P.</em> </li>
+ <li>Patch for the NORMALIZE_PATH builtin Boost
+ Jam rule as well as an appropriate update for the path.jam Boost Build module
+ where that rule was being used to implement path join and related operations.
+ -- <em>Jurko G.</em> </li>
+ <li>Fixed a bug causing Boost Jam not to handle
+ target file names specified as both short and long file names correctly. --
+ <em>Jurko G.</em> </li>
+ <li>Relaxed test, ignoring case of drive letter. --
+ <em>Roland S.</em> </li>
+ <li>Implemented a patch contributed by Igor Nazarenko
+ reimplementing the list_sort() function to use a C qsort() function instead of
+ a hand-crafted merge-sort algorithm. Makes some list sortings (e.g. 1,2,1,2,1,2,1,2,
+ ...) extremely faster, in turn significantly speeding up some project builds.
+ -- <em>Jurko G.</em> </li>
+ <li>Fixed a bug with bjam not handling the '' root
+ Windows path correctly without its drive letter being specified. -- <em>Jurko
+ G.</em> </li>
+ <li>Solved the problem with child process returning the value 259 (Windows
+ constant STILL_ACTIVE) causing bjam never to detect that it exited and therefore
+ keep running in an endless loop. -- <em>Jurko G.</em> </li>
+ <li>Solved the
+ problem with bjam going into an active wait state, hogging up processor resources,
+ when waiting for one of its child processes to terminate while not all of its
+ available child process slots are being used. -- <em>Jurko G.</em>
+ </li>
+ <li>Solved a race condition between bjam's output reading/child process termination
+ detection and the child process's output generation/termination which could have
+ caused bjam not to collect the terminated process's final output. -- <em>Jurko
+ G.</em> </li>
+ <li>Change from vfork to fork for executing actions on Darwin to improve
+ stability. -- <em>Noel B.</em> </li>
+ <li>Code reformatting and cleanups. --
+ <em>Jurko G.</em> </li>
+ <li>Implement ISFILE built-in. -- <em>Vladimir
+ P.</em> </li>
+</ul>
</p>
</div></description></item><item><title>Version 1.37.0</title><pubDate>Mon, 03 Nov 2008 12:00:00 GMT</pubDate><boostbook:purpose><span class="brief"><span class="purpose">
New Library: Proto. Updated Libraries: Asio, Circular Buffer, Dynamic Bitset,
Modified: website/public_html/beta/feed/downloads/bjam_3_1_17.qbk
==============================================================================
--- website/public_html/beta/feed/downloads/bjam_3_1_17.qbk (original)
+++ website/public_html/beta/feed/downloads/bjam_3_1_17.qbk 2008-11-29 00:16:55 EST (Sat, 29 Nov 2008)
@@ -9,6 +9,8 @@
]
[include ext.qbk]
+[template list[items]'''<itemizedlist>'''[items]'''</itemizedlist>''']
+[template li[text]'''<listitem>'''[text]'''</listitem>''']
[download http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941&release_id=643622]
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk