From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] Fix for building correct code on i386-pc (CVS-HEAD)
Date: Wed, 31 May 2006 02:31:49 +0200 [thread overview]
Message-ID: <200605310231.49399.okuji@enbug.org> (raw)
In-Reply-To: <1149026404.7177.103.camel@basalt.austin.ibm.com>
On Wednesday 31 May 2006 00:00, Hollis Blanchard wrote:
> On Tue, 2006-05-30 at 22:59 -0500, Harley D. Eades III wrote:
> > http://lists.gnu.org/archive/html/grub-devel/2006-05/msg00106.html
>
> "host" and "target" are unclear to me here. For example, grub-emu would
> be compiled for the "host", but grub itself would be for the "target"?
> When would you ever want to build things differently like that?
This is one of the requested features for GRUB. In GRUB Legacy, some group
developed GRUB on Sparc, but for PC by cross-compiling (actually, this was
Alcatel). It is a good thing that you can install GRUB for an architecture on
another.
Okuji
next prev parent reply other threads:[~2006-05-31 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 21:08 [patch] Fix for building correct code on i386-pc (CVS-HEAD) Vesa Jääskeläinen
2006-05-30 21:15 ` Hollis Blanchard
2006-05-31 3:59 ` Harley D. Eades III
2006-05-30 22:00 ` Hollis Blanchard
2006-05-31 0:31 ` Yoshinori K. Okuji [this message]
2006-05-31 21:00 ` [PATCH] Fix for configure on x86_64 (Was: Re: [patch] Fix for building correct code on i386-pc (CVS-HEAD)) Jeroen Dekkers
2006-06-01 15:39 ` Yoshinori K. Okuji
2006-06-07 11:16 ` [PATCH] Another fix for x86_64 Jeroen Dekkers
2006-06-07 15:55 ` Marco Gerards
2006-05-30 22:10 ` [patch] Fix for building correct code on i386-pc (CVS-HEAD) Marco Gerards
2006-05-31 0:28 ` Yoshinori K. Okuji
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=200605310231.49399.okuji@enbug.org \
--to=okuji@enbug.org \
--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.