From: Richard Henderson <rth@twiddle.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ppc64: Fix linker script
Date: Tue, 04 Oct 2011 08:35:11 -0700 [thread overview]
Message-ID: <4E8B27AF.8000508@twiddle.net> (raw)
In-Reply-To: <1317741292-28514-1-git-send-email-afaerber@suse.de>
On 10/04/2011 08:14 AM, Andreas Färber wrote:
> Since commit 8733f609 (Fix linker scripts) linking on Linux/ppc64 fails:
It occurs to me to wonder if we ought to simply auto-detect the presence
of the -Ttext-segment ADDR option. If that's present, don't override the
linker script and all the changes that might have been introduced therein.
r~
next prev parent reply other threads:[~2011-10-04 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 15:14 [Qemu-devel] [PATCH] ppc64: Fix linker script Andreas Färber
2011-10-04 15:17 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2011-10-04 15:35 ` Richard Henderson [this message]
2011-10-05 20:50 ` [Qemu-devel] " Alexander Graf
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=4E8B27AF.8000508@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 NNTP newsgroup(s).