#68257 closed defect (fixed)
clang-14 @14.0.6_1+analyzer: error: use of undeclared identifier 'XDR'
Reported by: | janmuennich (Jan Münnich) | Owned by: | Mark Mentovai <mark@…> |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | sonoma | Cc: | amake (Aaron Madlon-Kay), chrstphrchvz (Christopher Chavez), pspanja (Petar Španja), cjones051073 (Chris Jones), ith140 (Ian Hoffman), dbl001 (dbl) |
Port: | clang-14 |
Description
clang-14, installed as a depencency for virt-viewer, fails to build on macOS 14.0 Sonoma. See attached log.
Attachments (1)
Change History (27)
Changed 14 months ago by janmuennich (Jan Münnich)
Attachment: | main.log.tar.bz2 added |
---|
comment:1 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sonoma added |
---|---|
Port: | llvm-14 added; clang-14 removed |
Summary: | clang-14 @14.0.6_1+analyzer: Failes to build on Sonoma → clang-14 @14.0.6_1+analyzer: error: use of undeclared identifier 'XDR' |
comment:2 Changed 14 months ago by amake (Aaron Madlon-Kay)
Cc: | amake added |
---|
comment:3 Changed 14 months ago by chrstphrchvz (Christopher Chavez)
comment:4 Changed 14 months ago by chrstphrchvz (Christopher Chavez)
Cc: | chrstphrchvz added |
---|
comment:5 Changed 14 months ago by pspanja (Petar Španja)
Cc: | pspanja added |
---|
comment:6 follow-ups: 12 13 Changed 14 months ago by cjones051073 (Chris Jones)
The sanitizers often cause problems with clang, I have more issues with them than anything else. They are also not critical to using the compiler, so one option is we disable them on macOS14 until someone is able to look in more detail (I am on macOS13 and do not plan to update until the linker issues with Xcode 15 and GCC see some sort of resolution).
can I ask anyone running macOS14 to see if
clang-17 clang-16 clang-15
build for you on this OS ?
comment:7 Changed 14 months ago by cjones051073 (Chris Jones)
Port: | clang-14 added; llvm-14 removed |
---|
comment:8 Changed 14 months ago by cjones051073 (Chris Jones)
Ryan - The port failing here is clang-14, not llvm-14.
comment:9 Changed 14 months ago by cjones051073 (Chris Jones)
Cc: | cjones051073 added |
---|
comment:10 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
I changed the port field because I've observed we often place the top-level port name into the port field, rather than the affected subport name, particularly in cases of python & perl modules. However, subports are an implementation detail that users need not be aware of, so it's probably better if we stop that custom and use the affected port name in the port field in cases other than e.g. python & perl modules.
comment:11 follow-up: 17 Changed 14 months ago by cjones051073 (Chris Jones)
Indeed. You have to use the correct(sub)port name otherwise the links to track tickets in e.g. https://ports.macports.org/port/clang-14/details/ would be in the wrong port (llvm-14 not clang-14).
comment:12 Changed 14 months ago by janmuennich (Jan Münnich)
Replying to cjones051073:
can I ask anyone running macOS14 to see if
clang-17 clang-16 clang-15build for you on this OS ?
I was able to build all three on the same system without any issues.
comment:13 Changed 14 months ago by pspanja (Petar Španja)
Replying to cjones051073:
The sanitizers often cause problems with clang, I have more issues with them than anything else. They are also not critical to using the compiler, so one option is we disable them on macOS14 until someone is able to look in more detail (I am on macOS13 and do not plan to update until the linker issues with Xcode 15 and GCC see some sort of resolution).
can I ask anyone running macOS14 to see if
clang-17 clang-16 clang-15build for you on this OS ?
They all build perfectly fine.
Thanks for looking into this.
comment:14 Changed 14 months ago by cjones051073 (Chris Jones)
Thanks for the check.
I have excluded clang-14 and older from the fallback list
https://github.com/macports/macports-ports/commits/master
Someone should now open a second ticket against virt-viewer to not force the use of clang-14 on systems where it isn't supported (or just update to use the default fallbacks).
comment:15 follow-up: 18 Changed 14 months ago by cjones051073 (Chris Jones)
can you see if clang-14 now builds on macOS14 with [370d81aeeea14a617a17867c322f5f6cc3571cd2/macports-ports]?
comment:16 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ith140 dbl001 added |
---|
Has duplicate #68270.
comment:17 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to cjones051073:
Indeed. You have to use the correct(sub)port name otherwise the links to track tickets in e.g. https://ports.macports.org/port/clang-14/details/ would be in the wrong port (llvm-14 not clang-14).
Right, that is one of the problems I've observed. We don't really have a solution for that when a problem affects, for example, all of the subports of a python or perl module port. Manually listing every subport in the port field is tedious and not something I've seen done.
comment:18 Changed 14 months ago by pspanja (Petar Španja)
Replying to cjones051073:
can you see if clang-14 now builds on macOS14 with [370d81aeeea14a617a17867c322f5f6cc3571cd2/macports-ports]?
It builds without issues now, thanks for the quick fix!
comment:19 Changed 14 months ago by cjones051073 (Chris Jones)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:20 Changed 14 months ago by markmentovai (Mark Mentovai)
https://github.com/macports/macports-ports/pull/20625 should be a proper fix that doesn’t require disabling the sanitizers.
comment:21 Changed 14 months ago by Mark Mentovai <mark@…>
Owner: | set to Mark Mentovai <mark@…> |
---|
comment:22 Changed 14 months ago by Mark Mentovai <mark@…>
comment:23 Changed 14 months ago by dbl001 (dbl)
I am still getting the error on a 2021 iMac 27" (x86-64) with XCode 15.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_llvm-14/clang-14/work/llvm-project-14.0.6.src/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:1254:17: error: use of undeclared identifier 'XDR' :info:build CHECK_TYPE_SIZE(XDR);
comment:24 Changed 14 months ago by cjones051073 (Chris Jones)
I suspect you have not updated your ports tree to pick up the latest fixes…
Lots of errors of this sort in the log: