Hi Steve,
steve tell wrote:
guile-config (at least in 1.6.x) is a script started with
"#!/usr/bin/guile" or in this case, perhaps "#!/usr/local/bin/guile"
If there was a problem building or installing the interpreter (or
perhaps the shared libraries it needs?) that might explain this result.
Perhaps check the first line of guile-config, see if the path to guile
there makes sense, exists, is executable, and basicly works?
I thought about that. On my system (linux/bash), having a bad
interpreter gives a different error message:
$ cat test
#!/bin/foo
foo-commands
$ ls -l /bin/foo
-rw-r--r-- 1 root root 0 2006-12-05 09:11 /bin/foo
$ ./test
bash: ./test: /bin/foo: bad interpreter: Permission denied
But, now that I think of it, if I run tcsh instead:
$ ./test
./test: Permission denied.
So yes, it does seem likely now that the interpreter is bad. Gopi, what
shell are you using? tcsh?
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
