The value defined for ld must be the same, since otherwise one gets
effects like we had for generated PPC objects: The BFD page size was
0x10000, the ld page size 0x1000. Thus the data segment alignment forced
in the linker script didn't allow BFD to really start a new segment
(unless by accident a 0x10000 boundary was crossed as well). Hence our
libraries and executables only had one loadable segment (containing both
text and data), which neither of the three Haiku ELF loaders (in boot
loader, kernel, and userland) likes at all.
As a fix we force 0x1000 page size for target Haiku in a similar way it
is done for QNX.
git-svn-id: file:///srv/svn/repos/haiku/buildtools/trunk@15705 a95241bf-73f2-0310-859d-f6bbb57e9c96
The i386-pc-haiku no longer uses the BeOS BFD target emulation, but
its own. A few things are shared for both *-*-haiku machines now.
The PowerPC Haiku binutils and gcc build, but I wouldn't expect them
to really produce usable output yet. We'll see...
git-svn-id: file:///srv/svn/repos/haiku/buildtools/trunk@15381 a95241bf-73f2-0310-859d-f6bbb57e9c96
cross-compiling with BeOS target works.
- tweaked build-procedure to allow for proper generation of a i586-pc-beos
cross-compiler on LINUX.
- added documentation for creation of cross-compiler.
git-svn-id: file:///srv/svn/repos/haiku/trunk/buildtools@11255 a95241bf-73f2-0310-859d-f6bbb57e9c96
built during the make process. Before, it was being built during the
install process, when gcc might not be available, if the install goes
into an empty folder. Now, installs in empty folders work properly.
git-svn-id: file:///srv/svn/repos/haiku/trunk/buildtools@11253 a95241bf-73f2-0310-859d-f6bbb57e9c96
