Dale Visser <dale.vis...@gmail.com> wrote: > In the interest of helping, I attempted to follow the README instructions > on a CentOS machine. Perhaps most of target audience for Readable is > already very familiar with the GNU toolchain, but I am not (lately living > mostly in the Java/Maven world). I had to infer the need to go find the > 'autoreconf' download. That itself appeared to have a dependency on GNU M4 > and autoconf.
That is EXTREMELY helpful, thanks! Yes, you're right, those are "should have been documented but were not" steps. I'll modify the README to make those clear. The good news is that git, autoconf, and automake are *only* required if you use the development version (acquired via git). If you download a released version (a tarball), those requirements should disappear. > After doing a 'yum install m4 autoconf', I'm stuck at this > error in the autoreconf/configure script: > > ./configure: line 22: /usr/lib/scripts/acscripts/sanitize.sh: No such file > or directory I'm not sure what's going on. It's trying to pull in "acscripts"... but I don't know why. Can you try running this?: sudo yum install automake # install automake autoreconf -i # Note the "re" ./configure If that still fails, email *just* to me the file "configure", and tell me which version of CentOS. --- 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
