On Tue, Jan 27, 2009 at 06:33:47PM +0100, Javier Martín wrote: > > So you propose --target to be reused like this (a PS3 building GRUB2 for > an amd64 BIOS PC with Linux) : > ./configure --build=ppc64-linux --host=x86_64-linux-gnu --target=i686-pc > ^--compiling system ^--tools system ^--boot arch
I'm not proposing to change the way --target is used, only describing what its argument is supposed to mean, based on a comment from configure.ac. I agree that having to specify an OS for --target in command-line is odd too, but it's a different problem. Maybe we could ask the config.sub maintainer for a dummy value, such as "unknown" or so (I think Glibc had a --host for standalone -no OS- arm builds, perhaps we could use the same). > I think we already have a better-geared switch for that (--with-platform > it is?), which is currently used to distinguish between BIOS and EFI > boot code on both x86 and x86-64. --with-platform is an override for the default platform that is otherwise derived from target_vendor, AFAIK. -- 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
