public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98324] [11 Regression] bootstrap broken with a LTO build configured with --enable-default-pie Date: Wed, 23 Dec 2020 12:55:56 +0000 [thread overview] Message-ID: <bug-98324-4-1xhkWrUv20@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98324 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>: https://gcc.gnu.org/g:544f477536010f055c26bc959b18fccf67902750 commit r11-6314-g544f477536010f055c26bc959b18fccf67902750 Author: Nathan Sidwell <nathan@acm.org> Date: Wed Dec 23 04:50:00 2020 -0800 c++tools: Fix PIE [PR 98324] This adds --enable-default-pie support to c++tools, so that the sample server is build -fPIE if requested. PR bootstrap/98324 c++tools/ * Makefile.in: Add FLAGPIE. * configure.ac: Add --enable-default-pie support. * configure: Rebuilt.
next prev parent reply other threads:[~2020-12-23 12:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 17:34 [Bug bootstrap/98324] New: " doko at debian dot org 2020-12-16 17:56 ` [Bug bootstrap/98324] " nathan at gcc dot gnu.org 2020-12-16 20:14 ` nathan at gcc dot gnu.org 2020-12-21 14:33 ` nathan at gcc dot gnu.org 2020-12-22 13:22 ` nathan at gcc dot gnu.org 2020-12-23 8:23 ` doko at debian dot org 2020-12-23 12:55 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-23 12:56 ` nathan at gcc dot gnu.org 2021-12-15 14:34 ` rdiezmail-gcc at yahoo dot de
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-98324-4-1xhkWrUv20@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).