public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29514] Need to use -fPIE not -fpie
Date: Mon, 29 Aug 2022 20:39:54 +0000	[thread overview]
Message-ID: <bug-29514-131-JG6kpKNgSg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29514-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29514

Richard Henderson <rth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.37
             Status|NEW                         |RESOLVED

--- Comment #4 from Richard Henderson <rth at gcc dot gnu.org> ---
commit 51231c469b49fb3837590f40a93f88db9a20bb86
Author: Richard Henderson <richard.henderson@linaro.org>
Date:   Tue Aug 23 13:49:23 2022 -0700

    Makeconfig: Set pie-ccflag to -fPIE by default [BZ# 29514]

    We should default to the larger code model, in order to support
    larger applications built with -static -pie.  This should be
    consistent with pic-ccflag, which defaults to -fPIC.

    Remove the now redundant override from sysdeps/sparc/Makefile.
    Note that -fno-pie and -fno-PIE have the same effect.

    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    Tested-by: Carlos O'Donell <carlos@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2022-08-29 20:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-29514-131@http.sourceware.org/bugzilla/>]

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=bug-29514-131-JG6kpKNgSg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).