All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Solving the grub-pe2elf problem
Date: Mon, 10 Aug 2009 13:35:08 +0200	[thread overview]
Message-ID: <20090810113508.GD9344@thorin> (raw)
In-Reply-To: <1249706967.28996.2.camel@mj>

On Sat, Aug 08, 2009 at 12:49:27AM -0400, Pavel Roskin wrote:
> On Fri, 2009-08-07 at 22:39 +0200, Robert Millan wrote:
> 
> > I don't understand this.  Why is a requirement to install GNU binutils
> > unreasonable, whereas a requirement to install objconv is not?
> 
> Installing binutils can break the existing toolchain.  Installing
> objconv should not.
> 
> It's a good idea, as it would unify Apple and Cygwin support to some
> degree.

I would prefer if we didn't feed the NIH syndrome in those two platforms (the
rest of the world has settled on ELF, and it is still difficult for users of
those two OSes to produce that format).

That said, switching to objconv is an improvement.  I have nothing against it.

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



  reply	other threads:[~2009-08-10 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 13:46 Solving the grub-pe2elf problem Robert Millan
2009-08-07 14:01 ` Vladimir 'phcoder' Serbinenko
2009-08-07 14:06   ` Vladimir 'phcoder' Serbinenko
2009-08-07 16:20     ` Christian Franke
2009-08-07 17:27       ` Bean
2009-08-08 22:04         ` Christian Franke
2009-08-07 20:39     ` Robert Millan
2009-08-08  4:49       ` Pavel Roskin
2009-08-10 11:35         ` Robert Millan [this message]
2009-08-07 16:18 ` Christian Franke
2009-08-08  4:53 ` Pavel Roskin

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=20090810113508.GD9344@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.