From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Solving the grub-pe2elf problem
Date: Fri, 7 Aug 2009 22:39:48 +0200 [thread overview]
Message-ID: <20090807203948.GA16350@thorin> (raw)
In-Reply-To: <d7ead6de0908070706k5b594aech51d263164a6e7bc8@mail.gmail.com>
On Fri, Aug 07, 2009 at 04:06:11PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Fri, Aug 7, 2009 at 4:01 PM, Vladimir 'phcoder'
> Serbinenko<phcoder@gmail.com> wrote:
> > On Fri, Aug 7, 2009 at 3:46 PM, Robert Millan<rmh@aybabtu.com> wrote:
> >>
> >> Hi,
> >>
> >> I thought of a possible solution to the grub-pe2elf problem. It seems that
> >> it is burdensome to produce ELF binaries on Windows, but building PE binaries
> >> or even PE/win32 executables on GNU/Linux is not (thanks to Mingw32 toolchain
> >> which is available on most distributions).
> >>
> If you see pe2elf as being too much of a burden we may switch to
> objconv: http://www.agner.org/optimize/. It's already used in
> conjunction with Apple Mach-O toolchain. It's not a GNU project but is
> licensed under GPL.
I don't understand this. Why is a requirement to install GNU binutils
unreasonable, whereas a requirement to install objconv is not?
--
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-08-07 20:39 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 [this message]
2009-08-08 4:49 ` Pavel Roskin
2009-08-10 11:35 ` Robert Millan
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=20090807203948.GA16350@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.