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] New: Build process does not honor discovered path to "gnatmake" and "gnatlink" Date: Thu, 23 Feb 2023 20:11:56 +0000 [thread overview] Message-ID: <bug-108909-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108909 Bug ID: 108909 Summary: Build process does not honor discovered path to "gnatmake" and "gnatlink" Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: emr-gnu at hev dot psu.edu CC: dkm at gcc dot gnu.org Target Milestone: --- Created attachment 54521 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54521&action=edit Patch to resolve gnatmake build issue When attempting to build GCC 12.2 from released source: $ GNATBIND=gnatbind-12.1 GNATMAKE=gnatmake-12.1 ../gcc-12.2.0/configure --enable-languages=c,c++,ada,fortran --program-suffix=-12.2 {...blah blah...} {...} checking for x86_64-linux-gnu-gnatbind... gnatbind-12.1 checking for x86_64-linux-gnu-gnatmake... gnatmake-12.1 checking whether compiler driver understands Ada... yes {...much later...} mkdir -p ada/gen_il cd ada/gen_il; gnatmake -q -g -gnata -gnat2012 -gnatw.g -gnatyg -gnatU -I/build/gcc-12.2.0/gcc/ada gen_il-main /bin/sh: gnatmake: command not found make: *** [ada/stamp-gen_il] Error 127 This seems similar to PR 30541, in that if your system-level packages don't have the GNAT tools installed, but you have specified an alternate compiler path to Ada tools in the environment, the build scripts ignore the configure-guessed (or environment-specified) options, and just blindly call "gnatmake". Thus, the build fails. The fix is to change lines 21, 42, and 49 of gcc/ada/Make-generated.in to use "$(GNATMAKE)" instead of "gnatmake".
next reply other threads:[~2023-02-23 20:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-23 20:11 emr-gnu at hev dot psu.edu [this message] 2023-02-23 21:46 ` [Bug ada/108909] " emr-gnu at hev dot psu.edu 2023-02-26 17:45 ` 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@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: linkBe 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).