All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: grub-pe2elf
Date: Fri, 31 Jul 2009 16:46:32 +0200	[thread overview]
Message-ID: <20090731144632.GA14036@thorin> (raw)


Hi,

On a recent discussion on IRC, Bean pointed out that grub-pe2elf is essentially
a workaround for a bug in objcopy.

Bean explained that this bug is quite obvious.  It seems Christian sent them
a patch, but it hasn't been applied (I don't know if it was rejected, or just
ignored, Christian could you explain?).

Back in 2007, Christian proposed an ad-hoc solution for converting from PE to
ELF:

  http://lists.gnu.org/archive/html/grub-devel/2007-11/msg00174.html

which was rejected (see my comment and Marco's reply).

Later in July 2008, Bean added grub-pe2elf to the repository.

I keep thinking the same I thought in 2007.  I don't agree that we should
add such workarounds just because objcopy has a bug.  binutils is a GNU
program.  It is free software and community-maintained.  If it has bugs,
we should be working with them instead of reimplementing their work.

First of all, I'm worried that we have discussions to decide things and they
are later forgotten or ignored.  Bean, please can you provide some explanation
on what happened?

Also, I think this commit should be reverted (at least the part that adds
grub-pe2elf).  Also, I'd like to hear input on what happened with Christian's
binutils patch, why it wasn't applied, etc.

Nevertheless, it's not an obligation for us to support win32.  As long as we
can do it sanely, I'm fine with it, but I don't want to see GRUB dragged into
a situation in which we need to preserve win32 support at all costs.

Our primary target are GNU-based systems, as well as other free software
systems, specially those that rely on GRUB as their default bootloader.

-- 
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-07-31 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 14:46 Robert Millan [this message]
2009-07-31 18:27 ` grub-pe2elf Christian Franke
2009-08-01 14:25   ` grub-pe2elf Robert Millan
2009-08-01 15:06     ` grub-pe2elf Christian Franke
2009-08-02 21:31       ` grub-pe2elf Robert Millan
2009-08-03  9:33         ` grub-pe2elf Christian Franke
2009-08-03  9:53           ` grub-pe2elf Vladimir 'phcoder' Serbinenko
2009-08-03 20:29             ` grub-pe2elf Pavel Roskin
2009-08-04 20:30               ` grub-pe2elf Robert Millan
2009-08-04 21:45                 ` grub-pe2elf Christian Franke
2009-08-04 22:39                   ` grub-pe2elf Robert Millan
2009-08-04 20:22           ` grub-pe2elf Robert Millan
2009-08-04 21:04             ` grub-pe2elf Christian Franke

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=20090731144632.GA14036@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.