Ken Moffat wrote:
On Thu, 18 Aug 2005, Jean Razack wrote:
Hi,
I try a cross-compiling (x86_64 > i386).
OK, if you want to build a wholly 32-bit LFS from a 64-bit Suse you can
*try* using the 32-bit options from Ryan's cross-lfs scripts that I
referred to in my previous reply. That is, give it the host/target/build
options, but only build 32-bit wherever Ryan builds 32 and 64 stuff.
Clearly, at some point just passing -m32 to a multilib gcc will work,
but I've no experience of what you are trying to achieve.
If what you want is a fast 32-bit-only machine running LFS-6.1, why
not build from a 32-bit host system (with a 32-bit kernel) and save
yourself a lot of aggravation ?
My first question is, is it correct that �gcc �print-file specs� print
�/usr/lib64/�� ?
Sounds correct for the Suse multilib gcc (your host).
Then the other is that in �$LFS/tools/lib/� isn�t a �ld-linux-so.2� file.
But the file is in �/lib/�.
The straight x86 book is not wholly appropriate to building x86 from a
multilib x86_64. In theory, you don't need to build cross- tools
because your host's gcc can build them correctly with -m32. But, you
need to be clear what you are trying to achieve.
Is /lib/ld-linux.so.2 the file installed by Suse for 32-bit
applications ?
Did you install ld-linux-x86-64.so.2 into either /tools/lib or
/tools/lib64 ?
Ken
I don't see the point of cross-building 32 from 64 unless your building
multi-lib.
The cross-build part of multi-lib will allow a 32 bit build however as
Ken said your looking for a straight 32 build, stick the lfs live CD in
and build lfs 6.1 without issue, and you'll get an environment that
people can support you in easier.
Matt
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
