From: Paolo Bonzini <pbonzini@redhat.com>
To: Juan Quintela <quintela@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 09:54:01 +0200 [thread overview]
Message-ID: <4A681719.5050700@redhat.com> (raw)
In-Reply-To: <cover.1248294529.git.quintela@redhat.com>
> As requested for Anthony, we use as search path the output of:
>
> ld --verbose -v | grep SEARCH_PATH
>
> Anthony suggestion was to use a INCLUDE in the linker script, but it got
> complicated because we have a relative path, and we want to get it working
> with VPATH ....
>
> Then I decided to use a second linker script for the search path instead of
> one INCLUDE.
I don't understand one thing. Is this patch now using the linker script
for all architectures? If so, it should be enough to call it
LDFLAGS_USER and add LDFLAGS+=$(USER_LDFLAGS) where the configuration of
linker scripts used to be done in the Makefile--or not?
BTW, maybe now the -Wl,-shared trick for self-virtualization can be
replaced with -fpie (position independent executable)?
Paolo
next prev parent reply other threads:[~2009-07-23 8:32 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 ` Paolo Bonzini [this message]
2009-07-23 8:44 ` [Qemu-devel] Re: [PATCH 0/3 v3] Change search path for libraries for x86_64 linker script Juan Quintela
2009-07-23 9:06 ` Paolo Bonzini
2009-07-23 9:11 ` Juan Quintela
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=4A681719.5050700@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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.