mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Chen Wang" <unicorn_wang@outlook.com>
To: musl <musl@lists.openwall.com>
Subject: [musl] Question: looks musl-gcc doesnot support -no-pie
Date: Mon, 10 Apr 2023 17:09:31 +0800	[thread overview]
Message-ID: <MA0P287MB033243F8EBDEB1AB18236921FE959@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 313 bytes --]

Hello,

When I tried to build with musl-gcc with "-no-pie", I find the a.out still is still PIE. I checked the detailed gcc log with "-v" and I think with musl-gcc.specs, "-no-pie" will be overwrite and does not work.
I'm not sure if it is a bug with musl-gcc or designed as this?



Best Regards

Chen

[-- Attachment #2: Type: text/html, Size: 941 bytes --]

                 reply	other threads:[~2023-04-10  9:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=MA0P287MB033243F8EBDEB1AB18236921FE959@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM \
    --to=unicorn_wang@outlook.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).