Joe Ciccone wrote:
Brandon Peirce wrote: > I guess rather than hacking the uname one could alternatively hack the > config.guess in (each subdir of) each package, right? > Replace them with > > #!/bin/sh > echo i486-pc-linux-gnu In the end it just comes down to what you would rather do. Build and load a kernel module that when unloaded returns to its previous state. Or modify the source of every package that checks the target tripplet.
Point taken. I'm just trying to understand where the "hooks" are for coaxing the toolchain to "bend the rules". (Personally I actually prefer not to modify
the sources as a general rule.) But I also prefer to avoid messing with the host sysem! I didn't study the patch yet, but you say it's kernel module, so if one is building in a chroot then that still the host kernel. Tough choices... oh, well. host system. _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
