Recently,
I upgraded MiKTeX to the latest versions, and since then there are
problems when I try to build R and/or R packages.
I tried to build R 1.9.0 beta and R 1.8.1 patched
I am running Windows XP Pro, SP 1
MikTeX version is
This is e-TeX, Version 3.141592-2.1 (MiKTeX 2.4)
(preloaded format=latex 2004.3.27)
fpTeX version is
This is e-TeXk, Version 3.141592-2.1 (Web2c 7.5.2)
(format=latex 2004.3.23) 27 MAR 2004 21:58
With MiKTeX, it is not possible any more
do build documentation either for R itself or for packages,
I get the following error
! LaTeX Error: Command \middle already defined.
Or name \end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.45 \newlength{\middle}
With fpTeX, I can build R itself, but when I try to build packages,
I get
(c:/Program Files/TeXLive/texmf/tex/latex/graphics/color.sty
Package: color 1999/02/16 v1.0i Standard LaTeX Color (DPC)
(c:/Program Files/TeXLive/texmf/tex/latex/texlive/color.cfg
File: color.cfg 2001/08/31 v1.1 color configuration of teTeX/TeXLive
)
! Package color Error: No driver specified.
See the color package documentation for explanation.
Type H <return> for immediate help.
...
l.123 }
You should make a default driver option in a file
color.cfg
eg: \ExecuteOptions{dvips}
)
Both versions of TeX are installed the standard way,
without changes (except adding a few local LaTeX style files).
Is this happening to anybody else?
--
Erich Neuwirth, Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at
Phone: +43-1-4277-38624 Fax: +43-1-4277-9386
Prof Brian Ripley
2004-Mar-28 12:10 UTC
[R] Build problems on Windows with fpTeX and MiKTeX
The fptex problem has been reported as happening on Unix too. Rd.sty was
changed a little while ago, *but only* in 1.9.0 AFAIK. Does 1.8.1 patched
not work? I have no problem with fptex, and presume Duncan M does not
either, as he is distributing binaries of 1.9.0 beta.
My color.cfg is 1.0 from TeXLive rather than 1.1 and contains
\ifcase\x
% default case
\ExecuteOptions{dvips}%
\or
% pdfTeX is running in pdf mode
\ExecuteOptions{pdftex}%
\else
% VTeX is running
\ExecuteOptions{vtex}%
\fi
so I guess yours has been modified incorrectly (e.g. for use with MikTeX?)
It looks like your MikTeX is broken.
In any case, you don't need LaTeX to build packages, so what exactly were
you trying to do? Check them?
On Sun, 28 Mar 2004, Erich Neuwirth wrote:
> Recently,
> I upgraded MiKTeX to the latest versions, and since then there are
> problems when I try to build R and/or R packages.
> I tried to build R 1.9.0 beta and R 1.8.1 patched
The date of the beta is crucial.
> I am running Windows XP Pro, SP 1
> MikTeX version is
> This is e-TeX, Version 3.141592-2.1 (MiKTeX 2.4)
> (preloaded format=latex 2004.3.27)
>
> fpTeX version is
> This is e-TeXk, Version 3.141592-2.1 (Web2c 7.5.2)
> (format=latex 2004.3.23) 27 MAR 2004 21:58
>
> With MiKTeX, it is not possible any more
> do build documentation either for R itself or for packages,
> I get the following error
>
> ! LaTeX Error: Command \middle already defined.
> Or name \end... illegal, see p.192 of the manual.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H <return> for immediate help.
> ...
>
> l.45 \newlength{\middle}
>
>
> With fpTeX, I can build R itself, but when I try to build packages,
> I get
>
>
> (c:/Program Files/TeXLive/texmf/tex/latex/graphics/color.sty
> Package: color 1999/02/16 v1.0i Standard LaTeX Color (DPC)
>
> (c:/Program Files/TeXLive/texmf/tex/latex/texlive/color.cfg
> File: color.cfg 2001/08/31 v1.1 color configuration of teTeX/TeXLive
> )
>
> ! Package color Error: No driver specified.
>
> See the color package documentation for explanation.
> Type H <return> for immediate help.
> ...
>
> l.123 }
>
> You should make a default driver option in a file
> color.cfg
> eg: \ExecuteOptions{dvips}
>
> )
>
> Both versions of TeX are installed the standard way,
> without changes (except adding a few local LaTeX style files).
>
>
> Is this happening to anybody else?
>
>
>
>
--
Brian D. Ripley, ripley at stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595
On Sun 28 March 2004, Prof Brian Ripley wrote:> The fptex problem has been reported as happening on Unix too. Rd.sty > was changed a little while ago, *but only* in 1.9.0 AFAIK. Does 1.8.1 > patched not work? I have no problem with fptex, and presume Duncan M > does not either, as he is distributing binaries of 1.9.0 beta.On Linux RH9, TeX, Version 3.14159 (Web2C 7.3.1) (format=latex 2003.12.27), using r-devel rsync'ed this morning (1.9.0 beta (2004-03-28)), checking a package gives: -------------------------- (/home/rsb/topics/Rtobe190/lib/R/share/texmf/hyperref.cfg (/usr/share/texmf/tex/latex/graphics/color.sty Package: color 1999/02/16 v1.0i Standard LaTeX Color (DPC) (/usr/share/texmf/tex/latex/config/color.cfg) ! Package color Error: No driver specified. See the color package documentation for explanation. Type H <return> for immediate help. ... l.123 } You should make a default driver option in a file color.cfg ------------------------ but on r-patched 1.8.1 Patched (2004-02-17) everything is as it was: ------------------------ (/home/rsb/topics/Rtobe181/lib/R/share/texmf/hyperref.cfg Package color Info: Redefining color Blue on input line 2. Package color Info: Redefining color Red on input line 3. Package hyperref Info: Option `hyperindex' set `true' on input line 16. Package hyperref Info: Option `colorlinks' set `true' on input line 16. Package hyperref Info: Option `linktocpage' set `true' on input line 16. Package hyperref Info: Option `plainpages' set `false' on input line 16. ) ----------------------- The issues seem to be around lines 220-240 in share/texmf/Rd.sty, but could be related to hyperref.cfg in the same directory - the new Rd.sty includes the same code as is in hyperref.cfg - should this file still be there? My TeX is too elementary to know, I'm afraid, but if hyperref.cfg is renamed to something else, the *.dvi checks to completion using devel without error, with log: ----------------------- Package hyperref Info: Bookmarks ON on input line 1797. Package hyperref Info: Hyper figures OFF on input line 1816. Package hyperref Info: Link nesting OFF on input line 1821. Package hyperref Info: Hyper index ON on input line 1824. Package hyperref Info: Plain pages ON on input line 1829. Package hyperref Info: Backreferencing OFF on input line 1836. ----------------------- Renaming/removing hyperref.cfg is also suggested by its absence in the devel tarball, so this could be a result of rsync not deleting a stale and now unneeded file, which then gets read and used. My color.cfg says: ------------------------- \@ifundefined{pdfoutput}% {\let\pdfoutput\@undefined \ExecuteOptions{dvips}}% {\ifcase\pdfoutput \ExecuteOptions{dvips}% \else \ExecuteOptions{pdftex}% \fi}% -------------------------- I looked at this because I wanted to check packages I answer for on the beta version, and had deleted the original mails about this before meeting the same problem myself. Roger -- Roger Bivand Economic Geography Section, Department of Economics, Norwegian School of Economics and Business Administration, Breiviksveien 40, N-5045 Bergen, Norway. voice: +47 55 95 93 55; fax +47 55 95 93 93 e-mail: Roger.Bivand at nhh.no