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/98754] gnatmake no longer recognizes -P option Date: Tue, 19 Jan 2021 21:54:55 +0000 [thread overview] Message-ID: <bug-98754-4-hryoqnJo4M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98754-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98754 --- Comment #3 from Eric Reischer <emr-gnu at hev dot psu.edu> --- (Or some other more descriptive error indicating "gprbuild" was not found on the path, rather than acting as though you have borked the command-line options.)
prev parent reply other threads:[~2021-01-19 21:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-19 21:04 [Bug ada/98754] New: " emr-gnu at hev dot psu.edu 2021-01-19 21:11 ` [Bug ada/98754] " charlet at gcc dot gnu.org 2021-01-19 21:53 ` emr-gnu at hev dot psu.edu 2021-01-19 21:54 ` emr-gnu at hev dot psu.edu [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-98754-4-hryoqnJo4M@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).