From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <paolo.bonzini@gmail.com>,
Rene Rebe <rene@exactcode.de>, Paul Brook <paul@codesourcery.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH 4/4] Multiboot build system
Date: Thu, 18 Jun 2009 12:19:40 +0200 [thread overview]
Message-ID: <4A3A14BC.1070902@redhat.com> (raw)
In-Reply-To: <23AB4AED-56E3-4780-A487-56132D8D3593@suse.de>
>>> The relocations are always an issue. If you know about a magic
>>> compiler option that tells the compiler "scream of you find
>>> relocations", please tell me.
>>
>> You can do a normal ELF link and use readelf on the output.
>
> Hm I just tried to put in an external relocation (mov %eax, FOO) and ld
> already complained about it.
> What issue exactly were you talking about Paul?
Just in case you were confusing Paolo B. (me) with Paul B., my
suggestion was just a way to find relocations assuming ld would not
complain. Possibly Paul's (his) observation does not apply to binary
output.
Paolo
next prev parent reply other threads:[~2009-06-18 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 14:56 [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 1/4] Change bochs bios init order Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 3/4] Multiboot support Alexander Graf
2009-06-17 14:56 ` [Qemu-devel] [PATCH 4/4] Multiboot build system Alexander Graf
2009-06-17 15:16 ` Paul Brook
2009-06-17 15:23 ` Alexander Graf
2009-06-18 7:57 ` [Qemu-devel] " Paolo Bonzini
2009-06-18 10:16 ` Alexander Graf
2009-06-18 10:19 ` Paolo Bonzini [this message]
2009-06-17 15:30 ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg Blue Swirl
2009-06-17 15:32 ` Alexander Graf
2009-06-17 15:59 ` Anthony Liguori
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=4A3A14BC.1070902@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=kwolf@redhat.com \
--cc=paolo.bonzini@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
/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 NNTP newsgroup(s).