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.
