public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/106956] GCC 12.2.0 & Mac OS X Lion : make failed
Date: Fri, 16 Sep 2022 16:31:56 +0000 [thread overview]
Message-ID: <bug-106956-4-wW94aJI3H7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106956-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106956
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You're still using commas in your paths:
/Volumes/External_7/_Ze-Bins/_GNU-Compilers/_12,2.x/share/gcc-12.2.0/python
^
here
So this is the same problem.
*** This bug has been marked as a duplicate of bug 105819 ***
prev parent reply other threads:[~2022-09-16 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 15:38 [Bug regression/106956] New: " bug-reports.delphin at laposte dot net
2022-09-16 15:39 ` [Bug regression/106956] " bug-reports.delphin at laposte dot net
2022-09-16 15:40 ` bug-reports.delphin at laposte dot net
2022-09-16 16:31 ` redi at gcc dot gnu.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-106956-4-wW94aJI3H7@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).