Ralf Angeli <[EMAIL PROTECTED]> writes:
> The configuration succeeds (apart from some seemingly insignificant
> problem with changing back to the top level directory) if the
> "export EMACS" statement in the top level configure.ac is disabled
> or removed.
>
> Is this statement mandatory?
Probably not. It is intended to save the lower configure.ac from
repeating tests that would turn out the same, anyway.
> If I configure AUCTeX with something like `EMACS=/path/to/emacs
> ./configure --prefix=/some/prefix', the preview/configure script
> gets the given Emacs even if the statement is disabled. (... and
> the path in a set $EMACS will be used for all sorts of variables,
> like $lispdir, $packagelispdir, etc., instead of --prefix; don't
> know if this is correct)
>
> Anyway, after a succeeded configuration I am left with a top-level
> Makefile with the following paths:
>
> prefix = d:/tmp/foo\ bar/emacs-21.3$(null)
Fine.
> exec_prefix = ${prefix}$(null)
> libdir = ${exec_prefix}/lib$(null)
> packagedatadir = d:/tmp/foo bar/emacs-21.3/site-lisp/auctex$(null)
Not fine.
> datadir = ${prefix}/share$(null)
> localstatedir = ${prefix}/var$(null)
> infodir = ${prefix}/info$(null)
> lispdir = d:/tmp/foo\ bar/emacs-21.3/site-lisp$(null)
Fine.
> auctexstartfile=d:/tmp/foo\ bar/emacs-21.3/site-lisp/auctex.el
> packagelispdir = d:/tmp/foo bar/emacs-21.3/site-lisp/auctex$(null)
Not fine.
> packagedatadir = d:/tmp/foo bar/emacs-21.3/site-lisp/auctex$(null)
Not fine.
> Quoting is definitely messed up here. But I still don't know if
> this is a problem with the MSYS shell or our scripts.
I'd guess our scripts. Probably some AC_SHELL_QUOTIFY declarations
are missing or so.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
auctex-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/auctex-devel