#680 --elispdir' unrecognized

[Alex]

./configure --help in the root directory shows an --elispdir option, but it doesn't work:

$ ./configure honk --elispdir=elisp
executing /Library/Caches/Homebrew/clisp-2.49/honk/configure honk --elispdir=elisp
configure: error: unrecognized option: `--elispdir=elisp'
Try `configure --help' for more information.

It looks like it's just passing the options to src/configure, which doesn't have that option.

They both should probably instead recognize --with-lispdir, which seems more common especially in GNU software.

[Alex]

That terminal output was from when I was messing around with the directory argument, but it remains when I use src:

$ ./configure src --elispdir=elisp
executing /Library/Caches/Homebrew/clisp-2.49/src/configure src --elispdir=elisp
configure: error: unrecognized option: `--elispdir=elisp'
Try `configure --help' for more information.

[evoluisto]

dear all, i think thath the problem is, thath src/configure do not need elispdir, only makemake/.in.

i suggest this patch:

hg diff configure
diff -r b1477e46b3c9 configure
--- a/configure Sun Aug 14 00:13:57 2016 -0400
+++ b/configure Sun Aug 21 14:59:36 2016 +0100
@@ -382,11 +382,11 @@
         passnext=both ;;

       --elispdir=* | --elispdi=* | --elispd=* | --elisp=* | --elis=* | --eli=* | --el=*)
-        subdir_configure_args="$subdir_configure_args $arg"
+        #subdir_configure_args="$subdir_configure_args $arg"
         makemake_args="$makemake_args --elispdir="`getarg "$arg"` ;;

       --elispdir | --elispdi | --elispd | --elisp | --elis | --eli | --el)
-        subdir_configure_args="$subdir_configure_args $arg"
+        #subdir_configure_args="$subdir_configure_args $arg"
         makemake_args="$makemake_args --elispdir="
         prev=elispdir
         passnext=both ;;

[Bruno Haible]

./configure --help in the root directory shows an --elispdir option, but it doesn't work:

Thanks for the report. This is fixed in the hg repository now.

They both should probably instead recognize --with-lispdir, which seems more common especially in GNU software.

This would be too confusing, because in the context of clisp, "lisp" means "Common Lisp" not "Emacs Lisp".