From: Richard Henderson <rth@twiddle.net>
To: Ed Maste <emaste@freebsd.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Could configure generate QEMU's linker scripts?
Date: Mon, 20 May 2013 10:21:35 -0700 [thread overview]
Message-ID: <519A5B9F.6090507@twiddle.net> (raw)
In-Reply-To: <CAPyFy2AD87vdosCw0fzDroL-PyoFLfOQewVQiWeRvOEmfHy7uQ@mail.gmail.com>
On 05/19/2013 09:30 AM, Ed Maste wrote:
> On 19 May 2013 10:51, in a thread relating to the sparc-linux-user
> linker script, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> If we apply this for 1.5, it will be the first release of debian
>> package without extra fixes. Hopefully anyway :)
>>
>> (Ofcourse we may add more fixes later but... ;)
>
> Would it be reasonable to have QEMU's configure use sed or awk to
> start with ld's built-in linker script and transform it with the
> necessary modifications?
In general I believe that using the -Ttext-segment ADDR flag for ld
would completely obviate the need for even editing the link script.
> That is, it just changes the start address. Is this generally the
> only difference between QEMU's linker scripts and system built-ins?
Yes.
r~
next prev parent reply other threads:[~2013-05-20 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 16:30 [Qemu-devel] Could configure generate QEMU's linker scripts? Ed Maste
2013-05-19 19:24 ` Paolo Bonzini
2013-05-20 0:22 ` Aurelien Jarno
2013-05-20 17:21 ` Richard Henderson [this message]
2013-05-21 17:51 ` Ed Maste
2013-05-21 18:14 ` Richard Henderson
2013-06-02 17:15 ` Peter Maydell
2013-06-03 14:23 ` Richard Henderson
2013-06-03 14:57 ` Peter Maydell
2013-06-03 15:01 ` Richard Henderson
2013-06-04 15:55 ` Claudio Fontana
2013-06-04 16:13 ` Peter Maydell
2013-06-04 16:18 ` Richard Henderson
2013-06-05 9:03 ` Claudio Fontana
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=519A5B9F.6090507@twiddle.net \
--to=rth@twiddle.net \
--cc=emaste@freebsd.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@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).