From: Juan Quintela <quintela@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/3 v3] Change search path for libraries for x86_64 linker script
Date: Thu, 23 Jul 2009 11:11:32 +0200 [thread overview]
Message-ID: <m3tz139323.fsf@neno.mitica> (raw)
In-Reply-To: <4A68280B.30505@redhat.com> (Paolo Bonzini's message of "Thu\, 23 Jul 2009 11\:06\:19 +0200")
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 07/23/2009 10:44 AM, Juan Quintela wrote:
>> It is using the linker scripts for everything that was using it before,
>> not a single more, neither a single less.
>>
>> Just a bit of DRY, putting the commond code in a single place.
>
> Good, then it should be ok with respect to Paul Brook's remark.
That is my understanding. With respect t oPaul Brook remark, I don't
understand:
- how darwin-user don't use linker scripts
- why ia64 target softmmu uses it
But I guess that they are not fully functional yet can be a good
explanation.
Later, Juan.
prev parent reply other threads:[~2009-07-23 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 20:37 [Qemu-devel] [PATCH 0/3 v3] Change search path for libraries for x86_64 linker script Juan Quintela
2009-07-22 20:37 ` [Qemu-devel] [PATCH 1/3] our build system don't support mips little endian linux-user or bsd-user Juan Quintela
2009-07-22 20:37 ` [Qemu-devel] [PATCH 2/3] generate LDFLAGS for *-linux-user and *-bsd-user in a single place in configure Juan Quintela
2009-07-22 20:37 ` [Qemu-devel] [PATCH 3/3] set SEARCH_PATH for the linker script from output of ld --verbose -v Juan Quintela
2009-07-23 7:54 ` [Qemu-devel] Re: [PATCH 0/3 v3] Change search path for libraries for x86_64 linker script Paolo Bonzini
2009-07-23 8:44 ` Juan Quintela
2009-07-23 9:06 ` Paolo Bonzini
2009-07-23 9:11 ` Juan Quintela [this message]
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=m3tz139323.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--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 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.