Closed stephanstross closed 8 years ago
Hi @stephanstross
Thanks for the very detailed bug report! It looks as though Atom can't find the glslangValidator
executable.
If you load atom from the terminal via the atom
CLI command, simply adding /usr/local/bin
to your PATH
is enough.
Otherwise you need to specify the full path to glslangValidator in your config. You can do this by either:
linter-glsl
package to set glslangValidatorPath
to /usr/local/bin/glslangValidator
linter-glsl
section of your config to:"linter-glsl":
glslangValidatorPath: "/usr/local/bin/glslangValidator"
Let me know if that helps!
Nope. Same error :/ I've set the config option as you said, and the program is in there, but, no dice.
Ok, what does the output of ls -la look like?
$ ls -la /usr/local/bin/glslangValidator
Perhaps glslangValidator isn't executable for your user.
-rw-r----- 1 root root 3553816 Dec 24 22:06 /usr/local/bin/glslangValidator
It appears that it is not...
One quick sudo chmod +x /usr/local/bin/glslangValidator
later, and the output looks like this:
-rwxr-x--x 1 root root 3553816 Dec 24 22:06 /usr/local/bin/glslangValidator
and it looks like this! And, that being done, it seems to work now! No more error, and when I cause deliberate errors, it picks them up! Thanks for the help, and sorry about the late response.
[Enter steps to reproduce below:]
Happened after installing glslangValidator to /usr/local/bin/, following the instructions from the KhronosGroup.
Atom Version: 1.3.2 System: Ubuntu 15.04 Thrown From: linter-glsl package, v1.0.5
Stack Trace
Uncaught Error: spawn EACCES
Commands
Config
Installed Packages