Re: [AUCTeX] configure

[David Kastrup]

Fernando Benites <address@hidden> writes:

> Hi!  I am trying to install locally auctex, but the configure doesnt
> get my commands. make works but make install fails, here the
> configure output:
>
> configure --prefix=/homes/fbenites/ --without-texmf-dir 
> checking whether make sets $(MAKE)... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for date in ChangeLog... 2005-12-17
> checking for release in ChangeLog... 11.82
> checking for emacs... /usr/bin/emacs
> checking if /usr/bin/emacs is XEmacs... no
> checking for Emacs prefix... "/usr"
> checking if Emacs is recent enough... yes
> checking for mule support... yes
> checking if build directory is valid... yes
> checking where lisp files go... /usr/share/emacs/site-lisp
> checking what file to use for auctex startup... 
> /usr/share/emacs/site-lisp/auctex.el
> checking where the package lisp files go... /usr/share/emacs/site-lisp/auctex
> checking where the data files go... /usr/share/emacs/site-lisp/auctex
> checking where the info files go... ${prefix}/info
> checking where automatically generated global style hooks go... 
> ${localstatedir}/auctex
> checking for tex... /vol/tex/bin/tex
> checking for pdftex... /vol/tex/bin/pdftex
> checking for dvips... /vol/tex/bin/dvips
> checking for perl... /usr/bin/perl
> checking for makeinfo... /usr/bin/makeinfo
> checking for texi2html... /usr/bin/texi2html
> checking for texi2dvi... /usr/bin/texi2dvi
> checking for texi2pdf... /vol/tex/bin/texi2pdf
> checking for install-info... /vol/tex/bin/install-info
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating tex-site.el.out
> config.status: creating doc/Makefile
> config.status: creating auctex.el
> configure: configuring in preview
> configure: running /bin/sh './configure' --prefix=/homes/fbenites/  
> '--prefix=/homes/fbenites/' '--without-texmf-dir' --cache-file=/dev/null 
> --srcdir=.
> checking whether make sets $(MAKE)... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for /usr/bin/emacs... /usr/bin/emacs
> checking if /usr/bin/emacs is XEmacs... no
> checking for Emacs prefix... "/usr"
> checking if Emacs is recent enough... yes
> checking if build directory is valid... yes
> checking where lisp files go... /usr/share/emacs/site-lisp
> checking what file to use for preview startup... 
> /usr/share/emacs/site-lisp/preview-latex.el
> checking where the package lisp files go... /usr/share/emacs/site-lisp/auctex
> checking where the data files go... /usr/share/emacs/site-lisp/auctex
> checking where the info files go... ${prefix}/info
> checking for the location of AUCTeX's tex-site.el... ..
> checking for gs... gs
> checking for latex... /vol/tex/bin/latex
> checking for pdflatex... /vol/tex/bin/pdflatex
> checking for tex... /vol/tex/bin/tex
> Preview will be placed in /usr/share/emacs/site-lisp/auctex/latex
> Preview docs will be placed in /usr/share/emacs/site-lisp/auctex/doc
> checking kpathsea directory separator... ":"
> checking for texhash... /vol/tex/bin/texhash
> checking for initexmf... /vol/tex/bin/texhash
> checking for glaring installation conflicts... probably none
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating auto.el
> config.status: creating latex/Makefile
>
> Congratulations!  Configuration of preview is complete.
>
>
> Congratulations!  Configuration of AUCTeX is complete.
>
> Type "make" at the prompt to build.

Well, looks like you specified stuff for a user configuration, but you
don't actually have something like

/homes/fbenites/share/info
/homes/fbenites/share/emacs/site-lisp (in your load-path and present)
/homes/fbenites/texmf/tex/latex (present and visible to kpathsea)

So the configuration tries figuring out locations relative to the
Emacs binary instead, and those will not be writable by the user.

If your home directory does not have a "prefix" structure, you have to
manually specify where you want info directory, TeX files, Emacs
styles to end up, and those locations must be configured in the
respective programs by yourself.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum