From 4e9fb64d1d46a085eb66e90a13846b44f251efde Mon Sep 17 00:00:00 2001 From: dos-reis Date: Thu, 14 May 2009 00:37:05 +0000 Subject: * configure.ac.pamphlet: Tidy. --- ChangeLog | 4 ++++ configure | 18 +++++++++--------- configure.ac | 18 +++++++++--------- configure.ac.pamphlet | 18 +++++++++--------- 4 files changed, 31 insertions(+), 27 deletions(-) diff --git a/ChangeLog b/ChangeLog index c5d3757d..b5ff7911 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2009-05-13 Gabriel Dos Reis + + * configure.ac.pamphlet: Tidy. + 2009-05-13 Gabriel Dos Reis * configure.ac.pamphlet: Disable use of libtool to build shared diff --git a/configure b/configure index 9fa769d8..24f69ece 100755 --- a/configure +++ b/configure @@ -12803,28 +12803,25 @@ $as_echo "$as_me: error: --with-lisp=$axiom_lisp conflicts with --enable-gcl" >& ;; *) ## As of this writting, the Lisp systems ECL, GCL, SBCL, and CLisp all - ## understands the command line option --help, though they do - ## behave very differently. Some of them just print out the - ## help information and exits. Others, such as GCL, think they - ## must enter a read-eval-print loop (which isn't very helpful). + ## exist at the end of standard input. { $as_echo "$as_me:$LINENO: checking which flavor of Lisp" >&5 $as_echo_n "checking which flavor of Lisp... " >&6; } - what=`echo '(quit)' | $axiom_lisp --help` + what=`echo '(lisp-implementation-type)' | $axiom_lisp` case $what in *GCL*) axiom_lisp_flavor=gcl ;; - *ecl*) + *"ECL"*) axiom_lisp_flavor=ecl oa_standard_linking=yes ;; - *sbcl*) + *"SBCL"*) axiom_lisp_flavor=sbcl ;; - *CLISP*) + *"CLISP"*) ## Not all variants of CLisp have FFI support. FFI is used ## internally used by OpenAxiom in essential way. - if ! $axiom_lisp -q -x '*features*' | grep ':FFI' 2>/dev/null + if ! $axiom_lisp -q -x '*features*' | grep ':FFI' > /dev/null then { { $as_echo "$as_me:$LINENO: error: $axiom_lisp does not support Foreign Function Interface. Please upgrade to a better version of CLisp or install SBCL." >&5 $as_echo "$as_me: error: $axiom_lisp does not support Foreign Function Interface. Please upgrade to a better version of CLisp or install SBCL." >&2;} @@ -12832,6 +12829,9 @@ $as_echo "$as_me: error: $axiom_lisp does not support Foreign Function Interface fi axiom_lisp_flavor=clisp ;; + *"Armed Bear Common Lisp"*) + axiom_lisp_flavor=abcl + ;; esac { $as_echo "$as_me:$LINENO: result: $axiom_lisp_flavor" >&5 $as_echo "$axiom_lisp_flavor" >&6; } diff --git a/configure.ac b/configure.ac index 53fe5b52..ae648fe3 100644 --- a/configure.ac +++ b/configure.ac @@ -230,32 +230,32 @@ case $axiom_include_gcl,$axiom_lisp in ;; *) ## As of this writting, the Lisp systems ECL, GCL, SBCL, and CLisp all - ## understands the command line option --help, though they do - ## behave very differently. Some of them just print out the - ## help information and exits. Others, such as GCL, think they - ## must enter a read-eval-print loop (which isn't very helpful). + ## exist at the end of standard input. AC_MSG_CHECKING([which flavor of Lisp]) - what=`echo '(quit)' | $axiom_lisp --help` + what=`echo '(lisp-implementation-type)' | $axiom_lisp` case $what in *GCL*) axiom_lisp_flavor=gcl ;; - *ecl*) + *"ECL"*) axiom_lisp_flavor=ecl oa_standard_linking=yes ;; - *sbcl*) + *"SBCL"*) axiom_lisp_flavor=sbcl ;; - *CLISP*) + *"CLISP"*) ## Not all variants of CLisp have FFI support. FFI is used ## internally used by OpenAxiom in essential way. - if ! $axiom_lisp -q -x '*features*' | grep ':FFI' 2>/dev/null + if ! $axiom_lisp -q -x '*features*' | grep ':FFI' > /dev/null then AC_MSG_ERROR([$axiom_lisp does not support Foreign Function Interface. Please upgrade to a better version of CLisp or install SBCL.]) fi axiom_lisp_flavor=clisp ;; + *"Armed Bear Common Lisp"*) + axiom_lisp_flavor=abcl + ;; esac AC_MSG_RESULT([$axiom_lisp_flavor]) esac diff --git a/configure.ac.pamphlet b/configure.ac.pamphlet index 1069c09e..7a543893 100644 --- a/configure.ac.pamphlet +++ b/configure.ac.pamphlet @@ -885,32 +885,32 @@ case $axiom_include_gcl,$axiom_lisp in ;; *) ## As of this writting, the Lisp systems ECL, GCL, SBCL, and CLisp all - ## understands the command line option --help, though they do - ## behave very differently. Some of them just print out the - ## help information and exits. Others, such as GCL, think they - ## must enter a read-eval-print loop (which isn't very helpful). + ## exist at the end of standard input. AC_MSG_CHECKING([which flavor of Lisp]) - what=`echo '(quit)' | $axiom_lisp --help` + what=`echo '(lisp-implementation-type)' | $axiom_lisp` case $what in *GCL*) axiom_lisp_flavor=gcl ;; - *ecl*) + *"ECL"*) axiom_lisp_flavor=ecl oa_standard_linking=yes ;; - *sbcl*) + *"SBCL"*) axiom_lisp_flavor=sbcl ;; - *CLISP*) + *"CLISP"*) ## Not all variants of CLisp have FFI support. FFI is used ## internally used by OpenAxiom in essential way. - if ! $axiom_lisp -q -x '*features*' | grep ':FFI' 2>/dev/null + if ! $axiom_lisp -q -x '*features*' | grep ':FFI' > /dev/null then AC_MSG_ERROR([$axiom_lisp does not support Foreign Function Interface. Please upgrade to a better version of CLisp or install SBCL.]) fi axiom_lisp_flavor=clisp ;; + *"Armed Bear Common Lisp"*) + axiom_lisp_flavor=abcl + ;; esac AC_MSG_RESULT([$axiom_lisp_flavor]) esac -- cgit v1.2.3