public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28780] --disable-default-pie doesn't work
Date: Mon, 17 Jan 2022 13:23:32 +0000 [thread overview]
Message-ID: <bug-28780-131-JvV7OSItAz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28780-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28780
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Siddhesh Poyarekar from comment #3)
> (In reply to H.J. Lu from comment #0)
> > When glibc is configured with --disable-default-pie, glibc programs
> > and tests are still built with PIE.
>
> I don't see this:
>
> $ file iconv/iconvconfig
> iconv/iconvconfig: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
> BuildID[sha1]=aa0e3a52679c883c41e8919bf3c83d2042832abb, for GNU/Linux 3.2.0,
> with debug_info, not stripped
Does your toolchain default to PIE?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-17 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 23:11 [Bug build/28780] New: " hjl.tools at gmail dot com
2022-01-15 19:23 ` [Bug build/28780] " hjl.tools at gmail dot com
2022-01-15 19:39 ` hjl.tools at gmail dot com
2022-01-17 3:57 ` siddhesh at sourceware dot org
2022-01-17 13:23 ` fweimer at redhat dot com [this message]
2022-01-17 13:41 ` [Bug build/28780] --disable-default-pie doesn't work on static programs hjl.tools at gmail dot com
2022-01-17 13:58 ` siddhesh at sourceware dot org
2022-01-17 13:59 ` siddhesh at sourceware dot org
2022-01-17 15:27 ` cvs-commit at gcc dot gnu.org
2022-01-17 15:28 ` hjl.tools at gmail dot com
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-28780-131-JvV7OSItAz@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).