From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Building GRUB on platforms without ELF support
Date: Thu, 6 Dec 2007 13:08:15 +0100 [thread overview]
Message-ID: <20071206120815.GE13758@thorin> (raw)
In-Reply-To: <4741F21F.5020106@t-online.de>
On Mon, Nov 19, 2007 at 09:29:19PM +0100, Christian Franke wrote:
>
> It is not so easy:
>
> Cygwin's libbfd, ld and objcopy support elf32-i386, gas does not.
>
> But ld refuses to output elf32-i386 if pe-i386 is the input format. This
> restriction is hard-coded into ld because some pe-specific operations
> are hard-coded into bfd backend (This includes the hack which fixes the
> pc-relative relocation in the executable).
>
> Enable elf32-i386 as additional output format for gas does not work. The
> compilation fails, multiple emulations are not supported on i386 platform.
>
> But even building gas as a cross-assembler does not help. Some assembler
> directives, like symbol type specs, are output format specific. Output
> from Cygwin's gcc produces syntax errors.
>
> Therefore, you would need also a gcc build as a cross-compiler.
Can't the whole toolchain include ELF support as an alternative target? Kinda
like "-m32" on x86_64. I don't think it's unreasonable to request that Cygwin
provides this (and it'd probably solve other problems somewhere else).
Have you tried asking the Cygwin maintainers what they think about that?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-12-06 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 22:58 Building GRUB on platforms without ELF support Christian Franke
2007-11-18 7:07 ` Robert Millan
2007-11-18 11:35 ` Marco Gerards
2007-11-19 20:29 ` Christian Franke
2007-12-06 12:08 ` Robert Millan [this message]
2007-12-06 12:58 ` 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=20071206120815.GE13758@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.