On Fri, 27 Sep 2013 13:50:32 -0400, Dale Visser <dale.vis...@gmail.com> wrote: > I'm forwarding an earlier message to David below. He correctly diagnosed > the issue as needing a package named "expect" to be installed.
The instructions did mention "expect", but obviously they weren't clear enough. I've updated [Install-howto] to be MUCH more direct about that: http://sourceforge.net/p/readable/wiki/Install-howto/ I'll also modify the configure script so that it detects, and warns, if expect isn't available. This is *exactly* the kind of feedback/testing I was hoping for. Thanks very much! > Once I did > that, I could run the curly-guile script just fine, evaluating {2 + 3} to > 5. On CentOS, I used the --without-clisp option due to issues I hit. Excellent!! That's progress. > 1. It appears that libsigsegv and clisp both have to be installed > manually on CentOS 6.4. I never even pursued this to the stage of trying to > get ASDF installed. However, Guile was easy to get going. Hmm. You should only need libsigsegv if you're compiling clisp itself. I presume that's what you're doing? My hope would be that clisp has good directions for building and installing clisp. If that's not the case... then would you be willing to write directions on how to build/install clisp for CentOS/RHEL? We can stick that into a subsection, for those other poor people stuck in that situation :-). You can configure CentOS and RHEL to add additional repositories. E.G., you could add RepoForge (formerly RPMForge). I believe that has clisp: http://repoforge.org/use/ That would probably be easier than compiling it yourself. > 2. With little extra diligence on my part following the configuration > instructions in the clisp section of installation HOWTO, I got readable > running in clisp. Again Guile was easy to get going. I *did* notice in > the clisp REPL, I had to hit enter a second time before a one-liner > expression would print the result. Maybe this is a clisp thing...I'm not > familiar with it. If you're running "sweet-clisp", that'd be correct behavior. A sweet-expression reader will keep reading until it sees a blank line (the blank line is the terminator). Otherwise, it has no way of knowing if the next line will have some indented children or not. > 3. The "expect" dependency should probably be added to the install > documentation somewhere. My earlier success months ago with another Linux > version was probably just due to me being smarter that day and successfully > figuring out to look for the expect package. How's this?: http://sourceforge.net/p/readable/wiki/Install-howto/ --- David A. Wheeler ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
