From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: remove OS part of --target=xxx (Re: [PATCH] remove target_os)
Date: Sat, 7 Feb 2009 22:53:41 +0100 [thread overview]
Message-ID: <20090207215341.GI6343@thorin> (raw)
In-Reply-To: <1233077628.2937.7.camel@localhost>
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."
next prev parent reply other threads:[~2009-02-07 21:54 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
2009-01-27 17:33 ` Javier Martín
2009-02-07 21:53 ` Robert Millan [this message]
2009-01-27 17:21 ` 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=20090207215341.GI6343@thorin \
--to=rmh@aybabtu.com \
--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.