On Mon, Jan 26, 2009 at 08:57:10PM +0100, Christian Franke wrote: > But even if GRUB itself is build for some $target_cpu-$target_vendor > (i386-pc), the target_os is not useless if cross-compilation support is > desired: > > - GRUB tools like grub-setup are build for the target_os > - Package structure may depend on target_os.
That would be host_os. Consider this example: a system running on cpu FOO cross-compiles grub (i.e. stuff like grub-probe or grub-mkimage) so that it will run on cpu BAR. However, grub-mkimage should generate images for cpu BAZ (accordingly, the modules are built for BAZ too). This means build_cpu=FOO host_cpu=BAR target_cpu=BAZ. host_os, then, is the OS that runs on BAR. It isn't necessarily related to BAZ. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
