From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Solving the grub-pe2elf problem
Date: Fri, 07 Aug 2009 18:18:50 +0200 [thread overview]
Message-ID: <4A7C53EA.1040308@t-online.de> (raw)
In-Reply-To: <20090807134614.GA8719@thorin>
Robert Millan wrote:
> 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 building GRUB with "./configure --host=i586-mingw32msvc" works, we could
> include win32 binaries in the upcoming 1.97 release. Other GNU projects do
> this as well. Then we could drop support for toolchains that lack ELF.
>
>
Which binaries would you like to include?
- kernel.img and modules, and/or
- the grub-*.exe files (Note: mingw32 .exe != cygwin .exe).?
The problem with the PE->ELF conversion affects build of the *.mod
files, not the build of the *.exe. The linker script is necessary for
kernel.img.
> Christian and Bean, are you interested in implementing this?
>
>
No.
Then building a Cygwin package would rely on the existence of (tested or
untested?) binaries in the a release tarball. Building packages from SVN
snapshots would no longer be possible.
I really don't want to spent my open-source-time with such kind of
feature removal :-)
--
Regards,
Christian Franke
next prev parent reply other threads:[~2009-08-07 16:18 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
2009-08-07 16:18 ` Christian Franke [this message]
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=4A7C53EA.1040308@t-online.de \
--to=christian.franke@t-online.de \
--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.