qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: vr_qemu@t-online.de, marcandre.lureau@redhat.com
Subject: Re: [PATCH] meson: remove -no-pie linker flag
Date: Mon, 22 May 2023 08:54:05 -0700	[thread overview]
Message-ID: <e36730f8-5f32-1bfb-b09a-d6943732f0df@linaro.org> (raw)
In-Reply-To: <20230522080816.66320-1-pbonzini@redhat.com>

On 5/22/23 01:08, Paolo Bonzini wrote:
> The large comment in the patch says it all; the -no-pie flag is broken and
> this is why it was not included in QEMU_LDFLAGS before commit a988b4c5614
> ("build: move remaining compiler flag tests to meson", 2023-05-18).

It's not nearly as simple as that.

> +  # What about linker flags?  For a static build, no PIE is implied by -static
> +  # which we added above.  For dynamic linking, adding -no-pie is messy because
> +  # it overrides -shared: the linker then wants to build an executable instead
> +  # of a shared library and the build fails.  Before moving this code to Meson,
> +  # we went through a dozen different commits affecting the usage of -no-pie,
> +  # ultimately settling for a completely broken one that added -no-pie to the
> +  # compiler flags together with -fno-pie... except that -no-pie is a linker
> +  # flag that has no effect on the compiler command line.

-no-pie is a linker flag, but distro folk that didn't quite know what they were doing made 
local changes to gcc's specs file.  So it *is* a compiler command-line flag, but only for 
some builds of gcc.

We can't just remove -no-pie, we need to probe for it as cc.get_supported_arguments 
instead of cc.get_supported_link_arguments.

Or something.  It's a mess, for sure.


r~



  parent reply	other threads:[~2023-05-22 15:55 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 [this message]
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é
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=e36730f8-5f32-1bfb-b09a-d6943732f0df@linaro.org \
    --to=richard.henderson@linaro.org \
    --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).