-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0.6 may fail to build on macOS 14.3.1: error: unknown type name 'NSUInteger'
etc [reason unclear, worksforsome]
#112
Comments
Hi I'm developing on the same platform and version and have no trouble installing it. Have you changed anything on your system? I can also see that you are using macports, which might mess up everything. Have you tried installing it in the regular way? |
@thomasp85 Thank you for responding. This could also be a result of a recent Xcode 15.3 update, since nothing else should have changed, and Macports otherwise works perfectly fine. 1.0.5 was building across the board at least from 10.6 through 14: https://ports.macports.org/port/R-systemfonts/details |
ah - I have yet to update Xcode... It would seems strange if they messed with that, though... I'll give you an update when I try to reproduce with the latest Xcode |
Hmm... Also no issue after updating Xcode... Can I get you to post the full install log? |
@thomasp85 Well, while I am not sure what caused this issue at the moment, Apple did break some stuff in recent Xcode versions, so I won’t be surprised. Just recall a recent nightmare with I will be back to my testing hardware tomorrow, so can try building 1.0.6 on other systems. If it works with no changes on Catalina and Snow Leopard, then Sonoma is to blame. |
@thomasp85 The log attached: |
@thomasp85 UPD. This is definitely something either with Sonoma or with a specific Sonoma system. On Catalina
|
UPD2. However build on Sonoma keeps failing. I updated now to 14.4, nothing changed:
No idea why :( |
The big difference I can see is that you for some reason have hardcoded the SDK to MacOSX14.4.sdk in the last example. Maybe you have something weird in your global makevars or environment |
Hmm... I can see in my install log that despite upgrading Xcode, R still picks up the 14.2 version, not 14.4 |
Interesting. But how does it work? Does Xcode retain an older SDK, or the path points to nowhere? |
Trying to look into it now |
UPD3. Just for the record, 1.0.6 also builds normally on the old macOS 10.6 for
So everything else aside of Sonoma works for me so far. |
Ok, so I have now successfully got it to use the 14.4 sdk and I still have no issues compiling... Are you using the command line tools or have you somehow gotten R to use the Xcode tooling to compile? I've been told the later is ripe for disaster |
@thomasp85 From the logs it seems that the build uses command line tools:
But it may be some conflict with Xcode (?). I have added 1.0.6 update into my PR to Macports now, and CI already passed for macOS 13 and macOS 14. We could close the issue as |
One last idea... In the issue title you say macOS 14.3.1 - have you tried updating your OS so it matches the version of the build tools? |
error: unknown type name 'NSUInteger'
etcerror: unknown type name 'NSUInteger'
etc [reason unclear, worksforsome]
Yes, it is updated now:
And I reran build locally, it still fails. But given that CI pass, it should work (i.e. Macports is not to blame). And my Sonoma set-up should be pretty much default. |
@thomasp85 Update to 1.0.6 merged in macports/macports-ports@b76ac65 |
@thomasp85 Buildbots are fine on Sonoma. Build log: https://build.macports.org/builders/ports-14_arm64-builder/builds/20401/steps/install-port/logs/stdio So I am closing the issue. Though the reason of the failure is unclear, it worksforsome. Thank you for helping here! |
No problem. Sorry we couldn't get to the bottom of it |
I also encountered this problem. After I switched the sdk from 14.4 to 13.3, it became normal. |
It may not be an optimal solution, perhaps you could try different 14.x? There were changes across Xcode versions, chances are it works with another one. |
Something has broken down here.
The text was updated successfully, but these errors were encountered: