Tried on a Debian 7.1 system with very few backports, guile 1.8, NO
clisp, NO sbcl, and got:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for a sed that does not truncate output... /bin/sed
checking for env... /usr/bin/env
checking for guile... /usr/bin/guile
checking final decision HAVE_GUILE... yes
configure: No GUILE_SITE value has been forceably set.
checking asking guile for its site directory... /usr/share/guile/site
checking Guile site directory (GUILE_SITE)  ... /usr/share/guile/site
checking if (ice-9 readline) is available... yes
checking for scsh... no
checking final decision HAVE_SCSH... no

configure: WARNING: Prefix is not /usr; ensure ASDF is configured to
look at this Common Lisp dir.
checking Common Lisp lib dir (COMMON_LISP_LIB_DIR)... $(datadir)/common-lisp
checking for register-common-lisp-source... no
checking for unregister-common-lisp-source... no
checking whether ln -s works... yes
checking final decision HAVE_COMMON_LISP... yes
checking final decision HAVE_REGISTER_COMMON_LISP_SOURCE... no
checking final decision HAVE_UNREGISTER_COMMON_LISP_SOURCE... no
checking for clisp... no
checking final decision HAVE_CLISP... no
checking for sbcl... no
checking final decision HAVE_SBCL... no

checking default markdown command... python "$(srcdir)/markdown2.py"
-x link-patterns --link-patterns-file markdown-urls
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/dist-packages
checking final decision HAVE_MARKDOWN... yes
checking for expect... /usr/bin/expect

configure: creating ./config.status
config.status: creating Makefile

Looks fine, except for "checking final decision HAVE_COMMON_LISP...
yes", when I have neither clisp nor sbcl installed... I don't remember
installing any common lisp implementations (it's a pretty fresh
reinstall), so that part looks strange.  Not breakingly strange, just
strange.

On Tue, Oct 8, 2013 at 11:35 AM, David A. Wheeler <dwhee...@dwheeler.com> wrote:
> On Mon, 7 Oct 2013 15:17:12 -0400, Dale Visser <dale.vis...@gmail.com> wrote:
>
>> It worked nicely for me. The new, more verbose, warnings, are very helpful.
>
> Awesome!!  That's fantastic.
>
> If anyone else could give the updated version 0.9.4 a try, that'd be great.
>
>
> --- 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=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> Readable-discuss mailing list
> Readable-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/readable-discuss

------------------------------------------------------------------------------
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=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to