public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains 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 09:43:53 +0000 [thread overview]
Message-ID: <bug-111610-4-kK9dMeyrc0@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
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-09-27
Status|UNCONFIRMED |NEW
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
Hmm - so I guess you have no host-side dsymutil (e.g. built from LLVM) and do
something like symlink /usr/bin/true -> dsymutil?
I guess we have to fix configure to return an "unknown" for that.
----
As a matter of record, we do not really support cross-compilers targeting an
unknown Darwin version (the idea of xxx-apple-darwin [without a specific
version] was to support building natively on macOS). What will happen is you
will get the earliest supported OS version for the target arch (which might not
really be very representative)
It would likely be more representative/useful to choose some suitable OS
version:
e.g. powerpc-apple-darwin9 (latest) i686-apple-darwin17 (last 32b support)
x86_64-apple-darwin21 (up to date) .. and eventually aarch64-apple-darwin2x
....
Of course, the build should not fail so we must fix it - but just pointing out
that the results from the current builds are from a configuration that will be
issuing warnings about choice of OS version.
next prev parent reply other threads:[~2023-09-27 9:43 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 ` iains at gcc dot gnu.org [this message]
2023-09-27 11:35 ` [Bug target/111610] " 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
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-kK9dMeyrc0@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).