[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] remove target_os

From: Javier Martín
Subject: Re: [PATCH] remove target_os
Date: Tue, 27 Jan 2009 18:33:47 +0100

El mar, 27-01-2009 a las 18:51 +0200, Vesa Jääskeläinen escribió:
> Javier Martín wrote:
> > A, say, AMD64 Linux cross compiler hosted on x86 Cygwin would have
> > $build=i686-pc-cygwin and $host=amd64-linux-gnu. Thus, no conflict ought
> > to arise even with cross compilation enabled.
> > 
> > AFAIK, the full power of $build+$host+$target only matters when building
> > _compilers_ (and binutils, etc.), because you might want to use an
> > AMD64/Linux machine to build a compiler that will run on PPC/Darwin but
> > produce executables for a x86/Cygwin machine
> Now lets move this idea to GRUB 2:
> There is a build server is running on PPC/Linux and it wants to build
> all architectures supported by GRUB 2 (provide proper boot code for all
> arch and tools) and then makes software bundles (rpm,deb, or so) for all
> architectures.
> In example if all shell tools are to be ran on x86-64/Linux and then
> boot code needs to be compatible with x86-32 as there is PC-BIOS present
> on target system.

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 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.

> _______________________________________________
> Grub-devel mailing list
> address@hidden

Attachment: signature.asc
Description: Esta parte del mensaje está firmada digitalmente

reply via email to

[Prev in Thread] Current Thread [Next in Thread]