public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111610] Cannot build cross compiler to darwin targets after r14-4108-g47346acb72b50d
Date: Wed, 27 Sep 2023 13:42:09 +0000 [thread overview]
Message-ID: <bug-111610-4-ltSEpDhwlY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111610-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111610
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:
https://gcc.gnu.org/g:2ecab2f32b9e9a75bf563f80752d5b44dcd26b98
commit r14-4298-g2ecab2f32b9e9a75bf563f80752d5b44dcd26b98
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Wed Sep 27 11:05:31 2023 +0100
Darwin, configure: Allow for an unrecognisable dsymutil [PR111610].
We had a catch-all configuration case for missing or unrecognised dsymutil
but it was setting the dsymutil source to "UNKNOWN" which is not usable in
this context (since it clashes with an existing enum). We rename this to
DET_UNKNOWN (for Darwin External Toolchain).
PR target/111610
gcc/ChangeLog:
* configure: Regenerate.
* configure.ac: Rename the missing dsymutil case to "DET_UNKNOWN".
Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
next prev parent reply other threads:[~2023-09-27 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 9:25 [Bug target/111610] New: " jamborm at gcc dot gnu.org
2023-09-27 9:43 ` [Bug target/111610] " iains at gcc dot gnu.org
2023-09-27 11:35 ` jamborm at gcc dot gnu.org
2023-09-27 13:35 ` iains at gcc dot gnu.org
2023-09-27 13:42 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-27 13:49 ` iains at gcc dot gnu.org
2024-03-31 9:00 ` cvs-commit at gcc dot gnu.org
2024-04-25 19:24 ` cvs-commit 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-111610-4-ltSEpDhwlY@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).