public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nicolas at debian dot 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: Wed, 06 Apr 2022 15:24:58 +0000	[thread overview]
Message-ID: <bug-79724-4-ngaEU5PAru@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

--- Comment #10 from Nicolas Boulenguez <nicolas at debian dot org> ---
Hello.

I suggest that Homebrew adopt a solution tested for years by Debian:
* install the executables as TARGET-gcc-VERSION
* add symbolic links if necessary (gcc, gcc-VERSION, TARGET-gcc)
* apply the patch provided here over 3 years ago
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87777
  This URL always links to latest rebase:
 
https://salsa.debian.org/toolchain-team/gcc/-/blob/master/debian/patches/ada-gcc-name.diff

Until the assumptions are made explicit, the upstream code trying to guess the
name of the gcc executable will probably keep changing, as it has for at least
ten years. I have counted at least 6 similar bugs, and that’s only on Debian. 

This leads to duplicate efforts. For example, the diagnostic of this specific
index error is included in the patch above.

      parent reply	other threads:[~2022-04-06 15:24 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
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 [this message]

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-ngaEU5PAru@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).