public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "emr-gnu at hev dot psu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/108909] Build process does not honor discovered path to "gnatmake" and "gnatlink"
Date: Thu, 23 Feb 2023 21:46:19 +0000	[thread overview]
Message-ID: <bug-108909-4-Xp6XgJSoJl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108909-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108909

--- Comment #1 from Eric Reischer <emr-gnu at hev dot psu.edu> ---
One more:

--- gcc-12.2.0/gcc/ada/gcc-interface/Makefile.in        2022-08-19
04:09:52.352659553 -0400
+++ gcc-12.2.0-fixed/gcc/ada/gcc-interface/Makefile.in  2023-02-23
16:27:59.604161728 -0500
@@ -616,7 +616,7 @@
        -$(MKDIR) ./bldtools/oscons
        $(RM) $(addprefix ./bldtools/oscons/,$(notdir $^))
        $(CP) $^ ./bldtools/oscons
-       (cd ./bldtools/oscons ; gnatmake -q xoscons)
+       (cd ./bldtools/oscons ; $(GNATMAKE) -q xoscons)

 $(RTSDIR)/s-oscons.ads: ../stamp-gnatlib1-$(RTSDIR) s-oscons-tmplt.c gsocket.h
./bldtools/oscons/xoscons
        $(RM) $(RTSDIR)/s-oscons-tmplt.i $(RTSDIR)/s-oscons-tmplt.s

  reply	other threads:[~2023-02-23 21:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 20:11 [Bug ada/108909] New: " emr-gnu at hev dot psu.edu
2023-02-23 21:46 ` emr-gnu at hev dot psu.edu [this message]
2023-02-26 17:45 ` [Bug ada/108909] " ebotcazou at gcc dot gnu.org
2023-02-26 17:49 ` ebotcazou at gcc dot gnu.org
2023-02-26 17:55 ` cvs-commit at gcc dot gnu.org
2023-02-26 17:56 ` ebotcazou at gcc dot gnu.org
2023-03-06 10:40 ` cvs-commit at gcc dot gnu.org
2023-03-06 10:46 ` ebotcazou at gcc dot gnu.org
2023-04-26  6:57 ` rguenth at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2024-05-21  9:14 ` jakub 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-108909-4-Xp6XgJSoJl@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).