David Whitney wrote:
> Joe,
>
> Could please explain the statements you made below?  I am performing a 
> similar task to Luigi... I'm working on a i686 but I want to 
> cross-compile and build a system for an i586.
>
> Are you saying that when I am building the the CLFS System (starting 
> at Chapter 9), I need to "fake out" uname using an inserted kernel 
> module, or using a wrapper around the real uname?  Or is this 
> something that I need to do way before that ( i.e. when I am building 
> the cross-compiler)?
>
Pretty much the first one.
> Btw, which kernel do I modify... my system's kernel or the one built 
> in Chapter 12?
>
You load the module into the hosts kernel, what change would modifying 
the kernel in chapter 12 have on the build?
> Lastly, I need to understand if MACHTYPE and uname are related.  I 
> took and applied the suggestion you provided concerning how to get the 
> stripped down MACHTYPE in a Makefile.  When I test the result of my 
> ARCH variable (pre-chroot) it is set to i686.  When I am building the 
> CLFS System, should that not be i586?
They are related, just probably not in the way that you think. As I said 
in a previous email, $MACHTYPE is a pre-set variable in bash. When you 
configure a package, you see something along the lines of:

checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu

The target triplet is the host system type, that value will become 
$MACHTYPE in your current shell. If you were to run the bash you 
cross-compiled into /tools/bin you would see MACHTYPE=i586-pc-linux-gnu. 
But the one on your host system is i686-pc-linux-gnu.

How does configure determine these values? config.guess. if you run 
/usr/share/automake-*/config.guess you'll see the same detected value as 
above.

And finally where does config.guess get it's information? uname! 
config.guess is a bash script, open it up and check it out.
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to