From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel fixes for Cygwin
Date: Tue, 22 Jul 2008 18:58:57 +0200 [thread overview]
Message-ID: <488611D1.5070002@t-online.de> (raw)
In-Reply-To: <ca0f59980807210356w21d64b42o5ab33580359a6955@mail.gmail.com>
Bean wrote:
> On Mon, Jul 21, 2008 at 6:33 PM, Christian Franke
> <Christian.Franke@t-online.de> wrote:
>
>> Hi,
>>
>> due to the complexity of PE, a stand-alone converter may likely be
>> larger than the ~680 LoC converter I already offered here. It was
>> rejected, see this thread:
>> http://lists.gnu.org/archive/html/grub-devel/2007-11/msg00174.html
>>
>>
>
> Hi,
>
> I can't find the source code for your converter, perhaps you can repost it ?
>
>
I did not post it in the original thread from 2007-11.
It is actually a reduced version of objcopy with
- stuff not necessary for object format conversion removed,
- some functions from shared modules added to make it self-contained,
- the fix for the pc-relative relocation added to
It was intended as starting point to get rid of the hack in kern/i386/dl.c.
The hard work is still done by BFD.
> IMO, it's better to use our own tool, if it's not very complicated. I
> learn this lesson when writing efi support for x86_64. The gnu-efi
> toolchain can produce efi image, but it turns out to have some
> limitation on relocation, and it's hard to fix. I end up modifying
> grub-mkimage to support converting elf to pe32+. Relying on external
> tool means we are at the mercy of them, it's annoying when they have
> issue, as we can't expect upstream to fix it soon.
>
>
Yes, an own tool is probably best in the long term.
But such a tool will be likely not available for GRUB 1.97 tarball release.
Christian
next prev parent reply other threads:[~2008-07-22 16:59 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 [this message]
2008-07-21 11:02 ` Javier Martín
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=488611D1.5070002@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.