This fixes the problem that when updating binutils the installed GCC
still depends on binutils-2.23 and thus can't be used to recompile GCC
so that it then depends on binutils-2.24 instead (it's kind of a
circular dependency, but not a real one).
* portVersionedName contains the secondary architecture,
so using it means secondary package builds fail.
example: $portVersionedName is libwow_x86-0.0.0 when
doing an x86 build on x86_gcc2
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.
* Remove libiberty, move libbfs and libocodes to develop/lib.
* For the source package export only legacy/binutils.
* Change documentation directory to $docDir-$version.
