From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LRrAK-0001YO-Sb for mharc-grub-devel@gnu.org; Tue, 27 Jan 2009 11:51:56 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LRrAI-0001WF-7k for grub-devel@gnu.org; Tue, 27 Jan 2009 11:51:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LRrAG-0001Ub-Fy for grub-devel@gnu.org; Tue, 27 Jan 2009 11:51:53 -0500 Received: from [199.232.76.173] (port=44143 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LRrAG-0001UQ-6C for grub-devel@gnu.org; Tue, 27 Jan 2009 11:51:52 -0500 Received: from mta-out.inet.fi ([195.156.147.13]:56104 helo=jenni1.inet.fi) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LRrAF-0003m1-KJ for grub-devel@gnu.org; Tue, 27 Jan 2009 11:51:51 -0500 Received: from [192.168.1.102] (84.248.105.254) by jenni1.inet.fi (8.5.014) id 48FC59C704458780 for grub-devel@gnu.org; Tue, 27 Jan 2009 18:51:48 +0200 Message-ID: <497F3B98.6060504@nic.fi> Date: Tue, 27 Jan 2009 18:51:36 +0200 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: The development of GRUB 2 References: <20090125231241.GA27873@thorin> <497E1596.7040802@t-online.de> <1233008230.24663.8.camel@localhost> In-Reply-To: <1233008230.24663.8.camel@localhost> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: Quoted-Printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: [PATCH] remove target_os X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 16:51:54 -0000 Javier Mart=EDn wrote: > A, say, AMD64 Linux cross compiler hosted on x86 Cygwin would have > $build=3Di686-pc-cygwin and $host=3Damd64-linux-gnu. Thus, no conflict = ought > to arise even with cross compilation enabled. >=20 > AFAIK, the full power of $build+$host+$target only matters when buildin= g > _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.