-
Notifications
You must be signed in to change notification settings - Fork 41
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
MacOS: Permission errors #194
Comments
Manually changing permissions solved it of course but assume that it should work out of the box :) |
@grahambates Did I forget to change path names somewhere? |
No, the path names which contained version numbers were wrong at some point, but that was fixed before the current release. What's supposed to happen is that the extension chmods all the binaries on startup as the package is built on Windows and doesn't preserve permissions. Perhaps that's failing for some reason. @m4rkus did you see any error messages / output in VS Code to that effect? |
@grahambates Yes, don't remember exactly but it failed to resolve the path cc1 or something like that. I reinstalled the extension to find out what the exact error message was, but now I cannot reproduce the problem 🙃 |
I'm a bit stumped on this one. I'm wondering whether maybe it's happening in a specific state when updating from 1.6.7 -> 1.6.8 where it's running the new code, but still looking for the binaries in the old extension dir where the paths are different. If so this should hopefully be resolved by just restarting VS Code. |
Hello all, I am so grateful that you made this available for MacOS. Thanks a bunch. I have now updated to the latest 1.6.8, and initialized the demo project. When I build the demo source from VS Code (F5) I get the following errors:
I am running MacOS 13.2 Ventura, Silicon M1. I am using homebrew as a package manager (should that become relevant at some point..). I have tried to run manually the same thing ( I've exported the SDKDIR respectively):
Have you maybe encountered this already? Is there some dependency I am missing? Or further tempering necessary? |
shouldn't execute any clang while compiling amiga stuff... |
That's what puzzled me and why I tried to reproduce it manually invoking the provided executable:
And still getting the same clang warning:
|
I think even |
I'd guess that some of the other bundled binaries are still not executable and it's falling back to a system version on your path. |
Make sure you
|
Also make sure the relevant dirs are in your path when building manually. You can use the |
@grahambates Thank you kindly for the swift reply, I managed to compile and run the demo code. It was my mistake, I didn't see correctly while listing that the opt/m68k-amiga-elf was a directory and not file, so I didn't step into it and of course chmod +x was missing on the all the binaries in there. Sorry for the fuss. Once again @BartmanAbyss it's an awesome job you did with this extension and @grahambates porting to MacOS. |
No problem! Glad you got it working. |
Just in case you aren't aware, the executable flag is missing when you install the VSIX on a Linux box too |
I can confirm. Just installed from market place on Linux. Received similar errors:
|
Thanks a lot for the macOS support! There seems to be some kind of file permission problem with the extension.
I get this (VS Code Version: 1.74.0, macOS 13.0.1 (22A400), Apple Silicon) when compiling the test-project:
The text was updated successfully, but these errors were encountered: