* Not tested, a bug in haikuporter prevents from building it
* the tests fail on haiku because a path is hardcoded to /usr/include
in them. an upstream issue has been opened.
* Use current source revision.
* Copy and paste error in INSTALL(): installDir was used instead of
gccInstallDir. Notsure why the bootstrap recipe and this one use
different variable names.
* Fix stdc++ library symlink when built for secondary architecture.
The directory layout has changed similarly to that of the gcc 2 couple,
i.e. we install in develop/tools[/<arch>] instead of separate
subdirectories, so gcc finds the matching gas and ld.
Only tested the secondary architecture build so far.
* The files are no longer installed in a separate develop/tools
subdirectory for binutils and one for gcc. Instead we install
directly in develop/tools[/<arch>]. This allows gcc to find gas and
ld via its built-in search instead of via PATH only. In a hybrid
setup this makes a difference, when the gcc that is not the first in
PATH is invoked directly (e.g. via absolute path).
* Add support for building for the secondary architecture. Not tested
yet.
* prerequire cmd:gcc and cmd:ld
* use bootstrap.sh to bootstrap the build system, otherwise it fails to
generate aclocal from aclocal.in (which seems to be related to
timestamps, as an otherwise identical source folder [from the tree]
works fine) - hohum ...
* Rename version: 2.5_121012 -> 2.5_2012_10_12.
* Don't put Jambase.html, Jamfile.html into development directory.
While correct in principle, it is not so nice to separate them from
Jam.html, which is mostly development documentation as well
(documenting the tool invocation and the Jam language).
* Fix incorrect gccDate.
* For the source package only export legacy/gcc.
* architecture -> targetArchitecture
* Add missing provides for c++filt and i586-pc-haiku-gcc.
* Remove libiberty, move libbfs and libocodes to develop/lib.
* For the source package export only legacy/binutils.
* Change documentation directory to $docDir-$version.
