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 ada/104861] s-oscons.ads should use target_noncanonical
Date: Wed, 16 Mar 2022 08:22:40 +0000 [thread overview]
Message-ID: <bug-104861-4-Ynf9a3UDve@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104861-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104861
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:6a1150d1524aeda3381b2171712e1a6611d441d6
commit r11-9662-g6a1150d1524aeda3381b2171712e1a6611d441d6
Author: Richard Biener <rguenther@suse.de>
Date: Thu Mar 10 13:35:46 2022 +0100
ada/104861 - use target_noncanonial for Target_Name
The following arranges for s-oscons.ads to record target_noncanonical
for Target_Name, matching the install directory layout and what
gcc -dumpmachine says. This fixes build issues with gprbuild.
2022-03-10 Richard Biener <rguenther@suse.de>
PR ada/104861
gcc/ada/
* gcc-interface/Makefile.in (target_noncanonical): Substitute.
(OSCONS_CPP): Pass target_noncanonical as TARGET.
(cherry picked from commit 9467e7331188705ec16c086b77e1809c5b0aab7d)
next prev parent reply other threads:[~2022-03-16 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 7:37 [Bug ada/104861] New: " rguenth at gcc dot gnu.org
2022-03-10 9:20 ` [Bug ada/104861] " ebotcazou at gcc dot gnu.org
2022-03-10 9:29 ` ebotcazou at gcc dot gnu.org
2022-03-10 10:36 ` rguenther at suse dot de
2022-03-10 10:39 ` charlet at gcc dot gnu.org
2022-03-10 12:40 ` cvs-commit at gcc dot gnu.org
2022-03-16 7:18 ` rguenth at gcc dot gnu.org
2022-03-16 8:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-21 12:51 ` cvs-commit at gcc dot gnu.org
2022-04-21 12:58 ` rguenth at gcc dot gnu.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-104861-4-Ynf9a3UDve@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).