File boost-jam.changes of Package boost-jam

Fri Jun 12 09:00:38 UTC 2015 -

- Remove xz compressed archive
- Clenaup spec file with spec-cleaner
- boost-jam-codecleanup.diff was dropped

Fri Aug 24 17:28:18 CEST 2012 -

- Update to 20120824 from the boost-1.51.0 release.

Mon Jul  9 17:12:31 CEST 2012 -

- Repackage with bzip2 to have it build on older distributions.

Mon Mar 12 18:25:40 CET 2012 -

- Update to version 2011.04 from the boost-1.49.0 release.

Mon Feb 13 10:44:40 UTC 2012 -

- patch license to follow standard

Sat Sep 17 20:34:17 UTC 2011 -

- Remove redundant tags/sections from specfile

Mon Mar 14 12:45:46 CET 2011 -

- Update to 3.1.19.
- Recompress with xz.

Sat Apr 07 22:22:00 CET 2010 -

- Update to 3.1.18:
    and UPDATE_NOW.
  * Ensure all file descriptors are closed when executing actions complete
    on *nix.
  * Fix warnings, patch from Mateusz Loskot.
  * Add KEEP_GOING var to programatically override the '-q' option.
  * Add more parameters, up to 19 from 9, to rule invocations. Patch from
    Jonathan Biggar.
  * Print failed command output even if the normally quite '-d0' option.
  * Build of bjam with vc10, aka Visual Studio 2010.
  * More macros for detection of OSPLAT, patch from John W. Bito.
  * Add PARALLELISM var to programatically override the '-j' option.
  * Tweak doc building to allow for PDF generation of docs.
- clean up the SPEC file
- regenerated patches

Fri Feb 13 17:26:50 CET 2009 -

- Use -fno-strict-aliasing to make the program run on SLES9.

Tue Feb 10 14:33:05 CET 2009 -

- Update to 3.1.17:
  * Reflect the results of calling bjam from Python.
  * Try to work around at least one compiler bug with GCC and variable
    aliasing that causes crashes with hashing file cache entries.
  * 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.
  * Fix some possible overrun issues revealed by Fortify build. Thanks to
    Steven Robbins for pointing out the issues.
  * Handle \n and \r escape sequences.
  * Minor edits to remove -Wall warnings.
  * Dynamically adjust pwd buffer query size to allow for when PATH_MAX is
    default defined instead of being provided by the system C library.
  * Minor perf improvement for bjam by replacing hash function with faster
    version. Only 1% diff for Boost tree.
  * 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.
  * Removed the -xarch=generic architecture from build.jam as this option is
    unknown to the Sun compilers on Linux.
  * Fixed a bug with T_FATE_ISTMP getting reported as T_FATE_ISTMP &
    T_FATE_NEEDTMP at the same time due to a missing break in a switch
  * Fixed a Boost Jam bug causing it to sometimes trigger actions depending
    on targets that have not been built yet.
  * Added missing documentation for Boost Jam's :T variable expansion
    modifier which converts all back-slashes ('\') to forward slashed ('/').
  * 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.
  * Made all Boost Jam's ECHO commands automatically flush the standard
    output to make that output more promptly displayed to the user.
  * Made Boost Jam tests quote their bjam executable name when calling it
    allowing those executables to contain spaces in their name and/or path.
  * 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.
  * 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.
  * When importing from Python into an module with empty string as name,
    import into root module.
  * 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.
  * Fixed a bug causing Boost Jam not to handle target file names specified
    as both short and long file names correctly.
  * Relaxed test, ignoring case of drive letter.
  * 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.
  * 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
  * 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.
  * Code reformatting and cleanups.
  * Implement ISFILE built-in.

Fri Sep  5 13:29:46 CEST 2008 -

- Update to 3.1.16:

    * Plug memory leak when closing out actions.
    * Various improvements to __TIMINGRULE_ and __ACTIONRULE_ target 
      variable hooks.
    * Change JAMDATE to use common ISO date format.
    * Add test for result status values of simple actions, i.e.
      empty actions.
    * Fix buffer overrun bug in expanding @() subexpressions.
    * Check empty string invariants, instead of assuming all strings
      are allocated. And reset strings when they are freed.
    * Add OSPLAT=PARISC for HP-UX PA-RISC. -- Boris G.
    * Make quietly actions really quiet by not printing the command
      output. The output for the quietly actions is still available
      through __ACTIONRULE_.
    * When setting OSPLAT, check __ia64 macro.
    * Get the unix timing working correctly.
    * Add -fno-strict-aliasing to compilation with gcc. Which works
      around GCC-4.2 crash problems.
    * Increased support for Python integration.
    * Allow specifying options with quotes, i.e. --with-python=xyz,
      to work around the CMD shell using = as an argument separator.
    * Add values of variables specified with -s to .EVNRION module,
      so that we can override environment on command line.
    * Make NORMALIZE_PATH convert to /.

Fri Jul 27 20:22:29 CEST 2007 -

- Directly pass CFLAGS and RPM_OPTFLAGS to jam0 when bootstrapping
  (obsoletes the fix from Daniel Schepler) and pass
  -fno-strict-aliasing to gcc to fix the bjam segfault.
- Build optimized binary but don't strip it.

Tue Jul 24 19:39:15 CEST 2007 -

- fix early bjam segfault with gcc-4.2 (fix from Daniel Schepler)
- add testsuite from today's boost CVS and allow a maxium of 5 fails
- build debug binary by default, adds debuginfo package(thanks pth)

Thu Jul 19 17:45:04 CEST 2007 -

- Update to 3.1.14. Changes since 3.1.4:
  * Implement NATIVE_FILE builtin and several native rules.
  * Use default value of BOOST_BUILD_PATH is not is set in environment.

Sat May 27 23:54:47 CEST 2006 -

- Don't strip binaries.

Wed Jan 25 21:34:43 CET 2006 -

- converted neededforbuild to BuildRequires

Mon Oct 31 12:40:08 CET 2005 -

- don't build as root 

Wed May 26 11:51:27 CEST 2004 -

- added -fno-strict-aliasing

Fri May  7 17:33:59 CEST 2004 -

- honor RPM_OPT_FLAGS not only when bootstrapping
- build with -O1 on s390 (fixes boost) 

Wed Jul  9 09:39:54 CEST 2003 -

- Initial package creation.