public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cory Fields <lists@coryfields.com>
To: gcc@gcc.gnu.org
Subject: -static-pie and -static -pie
Date: Tue, 30 Jan 2018 18:26:00 -0000	[thread overview]
Message-ID: <CAApLimiqPc0BFqy28jDQXJH-A_cMzuJ9yD=ceeFM=gP0wnrysQ@mail.gmail.com> (raw)

Hi list

I'm playing with -static-pie and musl, which seems to be in good shape
for 8.0.0. Nice work :)

However, the fact that "gcc -static -pie" and "gcc -static-pie"
produce different results is very unexpected. I understand the case
for the new link-type, but merging the options when possible would be
a huge benefit to existing buildsystems that already cope with both
individually.

My use-case:
I'd like to build with --enable-default-pie, and by adding "-static"
to my builds, produce static-pie binaries. But at the moment, that
attempts to add an interp section.

So my question is, if no conflicting options are found, why not hoist
"-static -pie" to "-static-pie" ?

Regards,
Cory

             reply	other threads:[~2018-01-30 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 18:26 Cory Fields [this message]
2018-01-30 18:35 ` H.J. Lu
2018-01-30 19:07   ` Cory Fields
2018-01-30 19:15     ` H.J. Lu
2018-01-30 19:18       ` Cory Fields
2018-01-30 19:36         ` H.J. Lu
2018-01-31 15:44           ` Cory Fields
2018-01-31 15:56             ` H.J. Lu
2018-01-31 15:58               ` H.J. Lu
2018-02-02 18:21                 ` Rich Felker
2018-02-02 11:33             ` Szabolcs Nagy
2018-02-02 18:32               ` Rich Felker
2018-02-02 19:08 graham stott

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='CAApLimiqPc0BFqy28jDQXJH-A_cMzuJ9yD=ceeFM=gP0wnrysQ@mail.gmail.com' \
    --to=lists@coryfields.com \
    --cc=gcc@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).