public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/79724] GNAT tools do not respect --program-suffix and --program-prefix
Date: Mon, 03 Jan 2022 10:49:35 +0000 [thread overview]
Message-ID: <bug-79724-4-ppQPmqTavo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79724-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79724
Arnaud Charlet <charlet at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |charlet at gcc dot gnu.org
--- Comment #5 from Arnaud Charlet <charlet at gcc dot gnu.org> ---
Thanks for the investigation. What's tricky and why things got stuck last time
is the complexity of testing all the possible combinations (prefix, or suffix,
or both).
Can you in particular check that your proposed patch isn't breaking the use of
a prefix with no suffix (e.g. i686-elf-gcc) and check the behavior when using
both a prefix and a suffix (e.g. i686-elf-gcc-4.1)?
next prev parent reply other threads:[~2022-01-03 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-79724-4@http.gcc.gnu.org/bugzilla/>
2021-12-23 9:56 ` fxcoudert at gcc dot gnu.org
2021-12-23 10:18 ` fxcoudert at gcc dot gnu.org
2021-12-23 13:28 ` egallager at gcc dot gnu.org
2021-12-23 13:52 ` fxcoudert at gcc dot gnu.org
2022-01-03 10:49 ` charlet at gcc dot gnu.org [this message]
2022-01-04 14:24 ` fxcoudert at gcc dot gnu.org
2022-01-04 15:25 ` charlet at gcc dot gnu.org
2022-01-11 13:27 ` cvs-commit at gcc dot gnu.org
2022-01-11 13:30 ` charlet at gcc dot gnu.org
2022-04-06 15:24 ` nicolas at debian 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-79724-4-ppQPmqTavo@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).