From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, vr_qemu@t-online.de, marcandre.lureau@redhat.com
Subject: Re: [PATCH] meson: remove -no-pie linker flag
Date: Tue, 23 May 2023 09:18:32 +0100 [thread overview]
Message-ID: <ZGx22AySUhoZZuW1@redhat.com> (raw)
In-Reply-To: <CABgObfa+EG62MV-9xG7dtxiXj5ocosXS8kNneAoM_kTbmo0CbA@mail.gmail.com>
On Tue, May 23, 2023 at 10:02:51AM +0200, Paolo Bonzini wrote:
> On Tue, May 23, 2023 at 10:00 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > I'm curious why we need to do anything ? I would have thought that meson
> > should handle 'b_pie' itself, passing the right args to $CC that it feels
> > are appropriate. I don't recall seeing other apps using meson trying to
> > handle b_pie logic - what's special about QEMU ? IOW, is it possible to
> > delete this entire b_pie condition and thus avoid worrying about this
> > problem ?
>
> The issue is that Meson only has "enable PIE" or "leave PIE to the
> compiler default", while QEMU also has "disable PIE"---which is the
> messy one.
Does QEMU actually need "disable PIE" ? It existed in configure of
course, is there a reason we need to continue to support it in meson ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-05-23 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:08 [PATCH] meson: remove -no-pie linker flag Paolo Bonzini
2023-05-22 8:19 ` Philippe Mathieu-Daudé
2023-05-22 14:39 ` Richard Henderson
2023-05-23 7:23 ` Paolo Bonzini
2023-05-22 15:54 ` Richard Henderson
2023-05-23 7:52 ` Michael Tokarev
2023-05-23 5:57 ` Volker Rümelin
2023-05-23 8:00 ` Daniel P. Berrangé
2023-05-23 8:02 ` Paolo Bonzini
2023-05-23 8:18 ` Daniel P. Berrangé [this message]
2023-05-23 11:55 ` Paolo Bonzini
2023-05-23 13:14 ` Richard Henderson
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=ZGx22AySUhoZZuW1@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.de \
/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).