From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] remove target_os
Date: Tue, 27 Jan 2009 18:51:36 +0200 [thread overview]
Message-ID: <497F3B98.6060504@nic.fi> (raw)
In-Reply-To: <1233008230.24663.8.camel@localhost>
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.
next prev parent reply other threads:[~2009-01-27 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 23:12 [PATCH] remove target_os Robert Millan
2009-01-26 19:57 ` Christian Franke
2009-01-26 22:17 ` Javier Martín
2009-01-27 16:51 ` Vesa Jääskeläinen [this message]
2009-01-27 17:33 ` Javier Martín
2009-02-07 21:53 ` remove OS part of --target=xxx (Re: [PATCH] remove target_os) Robert Millan
2009-01-27 17:21 ` [PATCH] remove target_os Christian Franke
2009-01-27 17:40 ` Javier Martín
2009-01-27 19:56 ` Christian Franke
2009-01-27 21:52 ` Javier Martín
2009-01-29 7:00 ` Christian Franke
2009-02-07 21:54 ` Robert Millan
2009-02-08 19:59 ` Robert Millan
2009-02-07 21:48 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497F3B98.6060504@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.