public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110467] Bootstrap with Ada enabled fails with --enable-host-pie
Date: Fri, 30 Jun 2023 09:10:06 +0000 [thread overview]
Message-ID: <bug-110467-4-CPSIhMtWzL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110467-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110467
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2023-06-30
Status|UNCONFIRMED |NEW
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Confirmed, but
Author: Marek Polacek <polacek@redhat.com>
Date: Wed May 3 17:06:13 2023 -0400
configure: Implement --enable-host-pie
ada/
* gcc-interface/Make-lang.in (ALL_ADAFLAGS): Remove NO_PIE_CFLAGS. Add
PICFLAG. Use PICFLAG when building ada/b_gnat1.o and ada/b_gnatb.o.
* gcc-interface/Makefile.in: Use pic/libiberty.a if PICFLAG is set.
Remove NO_PIE_FLAG.
had first broken --enable-default-pie (and AFAICS was not approved by an Ada
maintainer), so the aforementioned change restored the previous working state.
next prev parent reply other threads:[~2023-06-30 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 19:37 [Bug bootstrap/110467] New: " mpolacek at gcc dot gnu.org
2023-06-28 19:38 ` [Bug bootstrap/110467] " mpolacek at gcc dot gnu.org
2023-06-30 9:10 ` ebotcazou at gcc dot gnu.org [this message]
2023-06-30 13:50 ` mpolacek at gcc dot gnu.org
2023-06-30 15:36 ` ebotcazou at gcc dot gnu.org
2023-07-01 14:41 ` mpolacek at gcc dot gnu.org
2023-07-05 11:12 ` simon at pushface dot org
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-110467-4-CPSIhMtWzL@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: 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).