From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel fixes for Cygwin
Date: Mon, 21 Jul 2008 13:02:58 +0200 [thread overview]
Message-ID: <1216638178.8334.153.camel@localhost> (raw)
In-Reply-To: <1KKshv-1kdy2C0@fwd33.aul.t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
El lun, 21-07-2008 a las 12:33 +0200, Christian Franke escribió:
> Bean wrote:
> > BTW, if you have time, you can consider writing a tool that convert pe
> > to elf directly, thus avoiding objcopy altogether. This shouldn't be
> > too difficult, you can take a look at util/i386/efi/grub-mkimage.c,
> > which does exactly the opposite, converting elf to pe32.
>
> due to the complexity of PE, a stand-alone converter may likely be
> larger than the ~680 LoC converter I already offered here.
Why do we even consider a PE->ELF converter? I think the easier way to
go would have the people building GRUB in cygwin (not exactly newbies)
to have an i386-pc-elf "cross compiler" built first, then use that for
the bootloader programs and the normal gcc for tools. Even a "naked"
(i.e. libraryless) cross compiler would work, since the bootloader part
of GRUB is does not need libs (in C terminology, it's "freestanding").
That way, we are free from "objcopy bugs" or "BFD design limitations".
This scheme is kinda like what's done with x86_64-pc-linux, with the
difference that in that case we use the same gcc for both "host" and
"target" by adding -m32 to the latter, but it's essentially the same
concept.
Habbit
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-07-21 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:51 [PATCH] Kernel fixes for Cygwin Christian Franke
2008-07-21 7:02 ` Bean
2008-07-21 7:25 ` Bean
2008-07-21 10:33 ` Christian Franke
2008-07-21 10:56 ` Bean
2008-07-22 16:58 ` Christian Franke
2008-07-21 11:02 ` Javier Martín [this message]
2008-07-21 11:16 ` Christian Franke
2008-07-21 15:51 ` Pavel Roskin
2008-07-21 16:50 ` Javier Martín
2008-07-21 17:03 ` Pavel Roskin
2008-07-21 17:23 ` Javier Martín
2008-07-21 19:59 ` Pavel Roskin
2008-07-21 10:21 ` 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=1216638178.8334.153.camel@localhost \
--to=lordhabbit@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.