From: "Jan Beulich" <JBeulich@novell.com>
To: <binutils@sourceware.org>
Subject: PE32/PE32+ linking of DLLs (and EFI applications)
Date: Mon, 02 May 2011 14:30:00 -0000 [thread overview]
Message-ID: <4DBEDC06020000780003F2F5@vpn.id2.novell.com> (raw)
How do ld-linked DLLs work when there don't seem to be any base
relocations getting emitted? While imo for DLLs this should be the
default anyway, is there a magic switch that I'm overlooking? EFI
applications also require relocations to be emitted...
While the hack called "dlltool" isn't really an option anyway, it's not
even possible to use it as the file generated with --base-file is empty
(I assume because data gets written to it only for COFF input files,
but on Linux all of the inputs are [obviously] ELF).
Thanks, Jan
next reply other threads:[~2011-05-02 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 14:30 Jan Beulich [this message]
2011-05-02 17:47 ` Joe Abbey
2011-05-03 7:45 ` Jan Beulich
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=4DBEDC06020000780003F2F5@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).