From: Aaron Lindsay <alindsay@codeaurora.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Liang Li <liang.z.li@intel.com>,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] avx2 configure: Use primitives in test
Date: Thu, 14 Jul 2016 15:44:55 -0400 [thread overview]
Message-ID: <20160714194455.GA13450@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA9qK4GM4DT=J7748s49XRHXftgR3qbmbpSE-o9kDUZsmQ@mail.gmail.com>
On Jul 14 15:35, Peter Maydell wrote:
> On 14 July 2016 at 15:27, Aaron Lindsay <alindsay@codeaurora.org> wrote:
> > On Jul 14 14:23, Peter Maydell wrote:
> >> On 14 July 2016 at 14:15, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >> > On 14/07/2016 15:13, Aaron Lindsay wrote:
> >> >> I'm configuring with:
> >> >> # ./configure \
> >> >> --static \
> >> >> --disable-gtk \
> >> >> --target-list=aarch64-softmmu
> >>
> >> > Hmm, it's possible that we have to disable ifunc together with --static.
> >>
> >> I'm still tempted to say we should just forbid building the softmmu
> >> binaries with --static, unless somebody has a serious use case for it...
> >
> > FWIW, we do find it convenient to be able to compile one binary capable
> > of running on multiple systems with different (and incompatible) library
> > versions.
>
> The difficulty here is that the system emulators may call
> functions in glibc which do dynamic resolution anyway, and so
> "require the shared libraries from the glibc version used for
> linking", to quote the linker warning. For the user-only binaries
> we can claim we don't make those function calls, but for softmmu
> we do.
We haven't observed any problems with this approach so far, but your
point is well taken. Perhaps we get what we deserve if we insist on
statically compiling ;-)
-Aaron
--
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2016-07-14 19:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 11:16 [Qemu-devel] [PATCH v3 0/2] AVX2 configure fixes Dr. David Alan Gilbert (git)
2016-06-10 11:16 ` [Qemu-devel] [PATCH v3 1/2] Make avx2 configure test work with -O2 Dr. David Alan Gilbert (git)
2016-06-10 11:16 ` [Qemu-devel] [PATCH v3 2/2] avx2 configure: Use primitives in test Dr. David Alan Gilbert (git)
2016-07-14 13:13 ` Aaron Lindsay
2016-07-14 13:15 ` Paolo Bonzini
2016-07-14 13:23 ` Peter Maydell
2016-07-14 14:27 ` Aaron Lindsay
2016-07-14 14:35 ` Peter Maydell
2016-07-14 19:44 ` Aaron Lindsay [this message]
2016-07-14 13:33 ` Dr. David Alan Gilbert
2016-07-14 14:18 ` Aaron Lindsay
2016-07-14 15:05 ` Dr. David Alan Gilbert
2016-07-14 19:36 ` Aaron Lindsay
2016-07-14 19:38 ` [Qemu-devel] [PATCH] avx2 configure: Disable if static build Aaron Lindsay
2016-07-19 19:12 ` Dr. David Alan Gilbert
2016-07-29 14:22 ` Peter Maydell
2016-06-13 9:31 ` [Qemu-devel] [PATCH v3 0/2] AVX2 configure fixes Paolo Bonzini
2016-06-13 10:51 ` Peter Maydell
2016-06-13 10:58 ` Dr. David Alan Gilbert
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=20160714194455.GA13450@codeaurora.org \
--to=alindsay@codeaurora.org \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=liang.z.li@intel.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).