From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Solving the grub-pe2elf problem
Date: Fri, 7 Aug 2009 16:01:39 +0200 [thread overview]
Message-ID: <d7ead6de0908070701lf0c082w92245d27f49fc256@mail.gmail.com> (raw)
In-Reply-To: <20090807134614.GA8719@thorin>
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 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.
>
I don't think that dropping useful features just for the sake of code
to look nice is a good thing. End users wouldn't care if you supply
binaries with or without compilable sources. But you don't let them to
exercise freedom. You can argue that you don't restrict their freedom
it's true but many people may need to taste freedom on a small thing
before changing to (w)holly free system. And this approach attracts
developpers. When I was speaking with developpers around Darwin they
specifically wanted to compile grub with toolchain they already have.
It's why I bothered at all to make grub compilable with Apple
toolchain (I'm personally fine with compiling it from Linux or
FreeBSD). I'm aware of few coders on different skill levels who are
now "tasting" grub and who wouldn't have if I haven't done it
> It probably doesn't currently build this way, because win32 won't have all
> the functions we need, but this can be fixed by importing them from Gnulib,
> the GNU compatibility library.
>
> Christian and Bean, are you interested in implementing this?
>
> Other maintainers, is it burdensome to any of you to include these binaries
> in official builds? I suppose it's not, since mingw32 packages are widely
> available, but it doesn't hurt to ask :-)
>
> --
> 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."
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-08-07 14:01 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 [this message]
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
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=d7ead6de0908070701lf0c082w92245d27f49fc256@mail.gmail.com \
--to=phcoder@gmail.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.