On 2014-11-05 14:42-0000 Arjen Markus wrote:

[...]
> xelatex failed
>
> "C:\Program:65: Package xparse Error: Support package l3kernel too old.
>
> "C:\Program:65: leading text:   }
>
> Unexpected error occured
>
> Error: xelatex compilation failed
>
> doc/docbook/src/CMakeFiles/pdf_target.dir/build.make:81: recipe for target 
> 'doc/docbook/src/plplot-5.10.0.pdf' failed
>
> make[2]: *** [doc/docbook/src/plplot-5.10.0.pdf] Error 1
>
> CMakeFiles/Makefile2:10018: recipe for target 
> 'doc/docbook/src/CMakeFiles/pdf_target.dir/all' failed
>
> make[1]: *** [doc/docbook/src/CMakeFiles/pdf_target.dir/all] Error 2
>
> Makefile:146: recipe for target 'all' failed
>
> make: *** [all] Error 2
>

> That is something I have no idea how to solve. There does not seem
to be an xelatex package under Cygwin and I have no clue as to the
nature of the "l3kernel" package.

> Any suggestions?

On Linux distributions and Cygwin you have to carefully distinguish
between package names and file names.

I don't know where you are looking for the xelatex file name and
l3kernel package name, but
there are something like 20 hits for xelatex and almost 10 hits for
l3kernel when you use the Cygwin
regex-based find web gui at <http://cygwin.com/cgi-bin2/package-grep.cgi>.
Furthermore, the portion of your error message I quoted above
mentioned "xelatex failed" which means you do have xelatex installed.

So the only relevant message above appears to be "Package xparse
Error: Support package l3kernel too old" which apparrently indicates
eith a temporary packaging issue or perhaps a more permanent packaging
error (no dependency on the Support package l3kernel so it doesn't get
updated at the right time compared to xelatex).  So I would simply do
a reinstall to see if that fixes it.

@BOTH: please mention (again and often) what Cygwin versions you are
using (e.g., 32-bit reinstalled on 2014-11-05). Cygwin has a rolling
distribution so the installation date matters a lot.  And, of course,
32-bit versus 64-bit matters a lot as well.  So the result could be
that Phil sails through and gets a near perfect result because he
lucked out on what date he reinstalled (or installed from scratch).  I
was in a similar situation with Wine as I followed its development
last year with something like 20 different commit id's spread over 6
months of development. I therefore learned to save the complete
Wine build and installation on any date so that my Wine results were always
reproducible, and I suggest both of you do the same with Cygwin.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to