-
Notifications
You must be signed in to change notification settings - Fork 10
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
Uncaught Error: spawn EACCES #42
Comments
I'm getting this error as well on startup, trying to get things setup to so I can build from atom correctly. I can run a build via the command line appropriately with the following command Stack Traceinternal/child_process.js:298 Error: spawn EACCES My setup is:Atom version: 1.3.2 ConfigHaxe path: "/usr/local/lib/haxe" Installed Packages
|
Seems that atom doesn't have the permissions to execute your haxe binary. Do you have anything custom in your haxe installation? |
The only thing is the path, when I tried to run haxelib setup to the default location it said it didn't have permission so I think that might be the actual issue. haxelib seems to be able to run fine but is installed to /usr/local/lib/haxelib Maybe related to this? HaxeFoundation/haxe#4483 I installed haxe with the default Mac OS X Installer from http://haxe.org/download/ which mentions the above thread "Make sure to check the changelog. In particular, this release fixes installation issues on OS X 10.11 'El Capitan', alongside with some C++, Java, C# and JS bug fixes." That's why in the settings I tried to specify the paths mentioned in the above Config. I also tried "usr/local/lib/haxelib" for the Haxelib executable path but it doesn't seem to make a difference. |
[Enter steps to reproduce below:]
Atom Version: 1.0.7
System: Mac OS X 10.10.5
Thrown From: haxe package, v0.8.7
Stack Trace
Uncaught Error: spawn EACCES
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: