Re: [AUCTeX-devel] Problem with Empty Dirs

[David Kastrup]

Ivan Savov <address@hidden> writes:

> I just pulled the latest XEmacs and the MinGW stuff in order to
> setup preview-latex which seems like the coolest thing since sliced
> bread.

Well, sliced previews, sliced bread, all the same.

> I followed the instructions and adapted them to my paths:
>
> ./configure --with-xemacs='C:\Program Files\XEmacs\XEmacs-21.4.13\i586-pc-win
> 32\xemacs'   --with-texmf-dir='E:/localtexmf' --with-packagedir='C:\Program 
> Fil
> es\XEmacs\xemacs-packages'
>
> (went through fine)

Ok, this is maximum Windows terror level for the scripts: file names
with back slashes and blanks in them.  The scripts are intended to
deal with that, but I think we had some recent fixes in that area
since 11.81.  Ralf?

> make (also worked with no prob)
>
> only
>
> make install
>
>
> gave me an error somewhere down the line and I quote:
>
> ___________________________________________________________
> address@hidden /c/Program Files/XEmacs/auctex-11.81
> $ make install
>
>  [snip]
>
> /bin/install -c -m 644 style/jsbook.el C:\\Program\
> Files\\XEmacs\\xemacs-packages/etc/auctex/style
>  /bin/install -c -m 644 style/babel.el C:\\Program\
> Files\\XEmacs\\xemacs-packages/etc/auctex/style
> for x in ; do \
>   echo ' /bin/install -c -m 644' $x 'C:\\Program\
> Files\\XEmacs\\xemacs-packages/lisp/auctex' ; \
>   /bin/install -c -m 644 $x C:\\Program\
> Files\\XEmacs\\xemacs-packages/lisp/auctex ; \
> done;
> /bin/sh: -c: line 1: syntax error near unexpected token `;'
> /bin/sh: -c: line 1: `for x in ; do  echo ' /bin/install -c -m 644' $x
> 'C:\\Program\ Files\\XEmacs\\xemacs-packages/lisp/auctex' ; 
> /bin/install -c -m 644 $x C:\\Program\
> Files\\XEmacs\\xemacs-packages/lisp/auctex ;  done;'
> make: *** [install-el] Error 2
> ___________________________________________________________
>
>
>>From what I gather this is a for loop trying to run (/bin/install -c)
> $x which is an empty variable. I can see how that can be a problem but
> I don't know how to go around it.
>
> Any tips?

I really seem to remember an error like that.  Do you have the
possibility to check out the current developer snapshot?  Uh, Reiner?
I forgot the link where you keep the prepackaged snapshots.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum