ANNOUNCE: SCons 0.98.5 (candidate for 1.0) fixes additional bugs

Version 0.98.5 of SCons has been released and is now available at the
SCons download page:

      http://www.scons.org/download.php

RPM and Debian packages and a Win32 installer are all available, in
addition to the traditional .tar.gz and .zip files.

This release is considered a candidate for the (long-awaited) official
1.0 SCons release.  We welcome and encourage widespread testing and use
of this release to try to identify any problems.  Please report your
bugs following the guidelines at:

      http://scons.tigris.org/bug-submission.html


WHAT'S NEW IN THIS RELEASE

This release contains fixes for various problems discovered in 0.98.1,
0.98.2, 0.98.3 and 0.98.4 with the intent of getting the fixes publicly
released while continuing to gather feedback on other possible 0.98.X
problems.

IMPORTANT:  Like its predecessors, this release officially deprecates
support for Python versions prior to 2.2 (that is, Python 1.5.2, 2.0
and 2.1).  SCons will function normally, but running SCons under any
deprecated Python version will generate a disableable warning message.
Our current plan is to support these deprecated Python versions in
SCons 1.0, and remove support in SCons 2.0.  If removing this support
would cause a problem for you, please contact the [email protected]
mailing list.

For a complete list of changes since the previous major release, see
the official change log:

      http://www.scons.org/CHANGES.txt

Here is a summary of the changes since the most recent 0.98.4 release:


FIXES

- The setup.py script on Mac OS X install SCons under /usr/local, not
  in the Mac OS X Python framework directories.
- The scons.bat file on Windows now returns the actual SCons exit status.
- The Intel C++ compiler ABI specification for EMT64 processors has been fixed.
- SCons now warns when trying to link C++ and Fortran object files into the
  same executable, instead of generated an error.
- The --interactive post-build messages no longer gets "stuck" reporting
  failures for all builds after the first failed target.
- Calling the File.File() object method has been fixed.


Thanks to Benoit Belley and David Cournapeau for their contributsion to
this release.

      --SK