Opened 3 months ago
Last modified 3 months ago
#70502 assigned defect
ccl: clang-9.0 dependency hinders installation on Sonoma 14.5 x86_64
Reported by: | kreuter (Richard Kreuter) | Owned by: | easye |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | catap (Kirill A. Korinsky) | |
Port: | ccl |
Description
clang-9.0 doesn't build successfully on MacOS Sonoma 14.5 x86_64. Does the ccl port have to stay on that clang version? (I was able to successfully install the port using a local portfile that called for Apple's clang 15.0. I don't know if that's appropriate for anybody else, just a data point.)
Change History (4)
comment:1 Changed 3 months ago by jmroot (Joshua Root)
Cc: | catap added |
---|---|
Owner: | set to easye |
Status: | new → assigned |
Summary: | clang-9.0 dependency hinders installation on Sonoma 14.5 x86_64 → ccl: clang-9.0 dependency hinders installation on Sonoma 14.5 x86_64 |
comment:2 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 3 months ago by easye
The whitelisting of clang 9 was added in [6e8dcf5b19bd6a31a175096f9b4dfdcb63326930/macports-ports] but the commit message doesn't say why.
At the time, I was working with a single macOS host that had compilation times for clang on the order of days so iterating through what worked was rather painful. I believe clang 9 was the first compiler that I was able to build that worked, so rather than testing all the other possible compilers, I probably just whitelisted what worked.
In general it's wrong for a port to whitelist a compiler as ccl does here. Instead ports should blacklist compilers that don't work and let MacPorts pick the next best compiler.
The whitelisting of clang 9 was added in [6e8dcf5b19bd6a31a175096f9b4dfdcb63326930/macports-ports] but the commit message doesn't say why.