Open barracuda156 opened 11 months ago
All of those errors are in files that are in /opt/local/libexec/llvm-15
and included by rgl
, they aren't in rgl
itself. So it's possible some define in rgl
is conflicting with one in those files, but it looks to me that it's more likely a problem completely outside of rgl
. If it's not something in your local configuration, it should be reported to the llvm-15
developers.
@dmurdoch This is unlikely to be LLVM issue or our set-up issue, since rgl
1.2.1 does build on every OS apart from Sonoma on aarch64
, it seems: https://ports.macports.org/port/R-rgl/details
The evidence that it builds everywhere else suggests that it is an issue with LLVM or your setup. If it's an rgl
issue, why does it only happen in that one particular configuration?
As I mentioned, it might be an rgl
issue. I might be including things in an illegal way that other compilers tolerate, or I might be defining things that I shouldn't. But I don't have a Sonoma system to test on, so if you want this fixed, I think you're going to have to track it down.
I'd start by drastically simplifying the build. Delete as much of rgl
as you can while still generating at least one of the errors you saw, and not introducing others. You should be able to get down to just one .cpp file and a small number of .h files. At that point maybe you'll spot an error in rgl
and I'll fix it, or maybe you won't, and you'll have to look elsewhere.
@dmurdoch Turns out this error happens only if X11 is enabled. Without X11 it builds fine.
As a dirty fix to unbreak the port, I will conditionally disable X11. But if you have an idea why specifically X11 introduces a locale-related breakage on Sonoma, please update me.
rgl
1.2.1 does build on every OS apart from Sonoma onaarch64
, it seems: https://ports.macports.org/port/R-rgl/details
At present, that URL shows that rgl 1.2.1 builds successfully on every macOS version and architecture that the MacPorts automated build machines have attempted to build it on. It does not show a failure on Sonoma arm64; it shows that no builds have been attempted on Sonoma arm64, which is because I have not yet set up a Sonoma arm64 build machine for MacPorts.
@ryandesign It fails to build locally on Sonoma aarch64. I know there is no buildbot atm.