Closed spelufo closed 9 years ago
@spelufo what version of scheme48 do you have installed? It must be precisely version 1.9.2
.
OK, that explains it. I have 1.9-3
, which is what there was apt-get installs by default.
Ok, in this case you'll want to uninstall that and install scheme48 from source. The later versions actually have changes that are significant to scsh's proper functioning.
Sorry this wasn't obvious, I'm going to find a way to have the build system detect and let the user know about issues like this.
I'm having the same problem; removing 1.9-3, installing 1.9.2 (per instructions at http://www.s48.org/1.9.2/download.html) didn't change anything. I still get "No such file or directory" even though my shell sees go and scsh, and has the latter installed in /usr/local/bin.
Someone else using scsh reported the same error several years ago in this thread: http://www.linuxquestions.org/questions/linux-general-1/shell-not-seeing-file-that-exists-562423/
@xhevahir did you rebuild scsh after installing the correct s48 version?
If so, could you start from scratch and post a gist with the steps you take to install / build s48 and scsh?
Yes, I rebuilt scsh after I installed scheme48 from www.s48.org; scheme48 works, and reports its version number as scheme48-1.9.2.
I actually have never posted a gist before and am not sure how to do so. Here are the commands I entered: https://gist.github.com/xhevahir/6e2a80c1476d6e60f34b
@xhevahir that's close, but it would be even more useful with the output of each command interleaved between those calls; essentially exactly what you're seeing on your terminal when you're going through this process. The output of ./configure
and make
in scsh would be particularly illuminating.
I posted another gist. I converted it from the log file and then copy-pasted it from a text editor, but I couldn't clean all of the control characters and other garbage from it.
@xhevahir in the scsh directory, try running make clean
and then make
/ make install
. What is the platform you're running this on, btw?
That did it! (I'm on Linux Mint XFCE 17.1, x86-64.) Thanks a lot for your help.
great :)
Just for your knowledge, this is what was happening: without make clean
your call to make
wasn't doing anything. It saw that all the build artifacts that you wanted were already there so it didn't waste time remaking them. But you actually wanted it to remake them since the artifacts were incorrectly made the first time. make clean
should remove all the build artifacts that make
originally produced, so that the next call to make
starts from scratch.
I'm on Linux Mint 17 Cinnamon 64-bit.