-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, May 01, 2007 at 03:37:31AM -0400, Robert P. J. Day wrote: > > (another bit of fallout from yesterday's cross-compiling adventure > ... if this is a bit incoherent, it's late.) > > in cross-compiling the kernel for x86_64, i had the location of the > toolchain in my search path and all of my config and build commands > were of the form: > > $ make ARCH=x86_64 CROSS_COMPILE=x86_64- ... > > for targets like > > ... defconfig > ... menuconfig > ... bzImage > ... modules > > so far, so good. > > then, even though it was certainly redundant, i left the ARCH= and > CROSS_COMPILE= make variables there when i did: > > # make ... modules_install > # make ... install > > first, i'm guessing that, regardless of architecture or > cross-compile, you can always run simply "make modules_install", No, "modules_install" also cd's to arch/$ARCH and installs modules over there. Same for the "install" target, but in this case to install the actual kernel (and running lilo, or whatever way to make the new kernel bootable). Erik - -- They're all fools. Don't worry. Darwin may be slow, but he'll eventually get them. -- Matthew Lammers in alt.sysadmin.recovery -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGN24D/PlVHJtIto0RAvDaAJwOOhsjHEmHKTvbqV6t9orpSYjy5ACfSYbh 5UO+raI+9ixcGscV2AwEfnU= =s9v4 -----END PGP SIGNATURE----- -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
