On Mon, Oct 22, 2007 at 05:31:36PM +0200, Tobias Vogel wrote:
> yes, i'm using the stable 1.0.0 clfs book and i'm right now stuck at
> chapter 10.7:
>
>
> Installing Basic System Software: Glibc-2.4
>
> my host-stytem is not old though, i'm using a fedora 7 on a
> amd64-machine with
> kernel 2.6.22.9, and so far there where no errors within the
> clfs-build-process, what
> makes that error look quite strange to me now. working in the
> chroot-jail right now,
> what makes me wonder even more about the fact that it's an x86_64-issue,
> as the target
> system should be a 486-system..?
In chroot ? So, you are planning to build it _all_ on the x86_64
before transferring it to the 486 ? That is _not_ what the stable
book expects you to do.
Your immediate problem is fairly obvious:
>
> the configure-output seems quite normal to me:
>
> root:/sources/glibc-build# ../glibc-2.4/configure --prefix=/usr
> --disable-profile --enable-add-ons --enable-kernel=2.6.0
> --libexecdir=/usr/lib/glibc
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
Those last 2 lines are only normal if you are building for x86_64.
And yes, in chroot on x86_64 the system will respond to 'uname -m'
with x86_64 if the kernel is 64-bit.
Basically, if you are following the 1.0.0 x86 book on x86_64, you
should use the 'if you are going to boot' option and build a 32-bit
kernel, copy it over, and then build chapters 9 and 10 on the target
board.
You _might_ be able to use 'linux32' on your host system to build
in chroot, but that will be a _major_ deviation from the book and
will probably need some other action (uname hacks) to build the
whole system for i486. You are likely to build at least some parts
of the system for i686, and debugging the resulting mess will not be
pleasant (you would need to attempt to compile the whole system, and
transfer it all, before you knew how much of it was built for i686).
By following the 'boot' option (chapter 7) and then transferring to
the target system, you can find out fairly quickly if any of the
temporary system has been built for i686 (possible, i{3..5}86 are
now a path less travelled), and hopefully you will build native i486
code for the final system.
Take a look at the archives for people trying to build for
i{3..5}86, and have a look at the sysroot book.
ĸen
_______________________________________________
Clfs-support mailing list
Clfs-support@lists.cross-lfs.org
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
