This is the mail archive of the
mailing list for the Cygwin project.
Re: texlive-install: core dumped
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Sat, 29 Jun 2013 18:46:28 -0400
- Subject: Re: texlive-install: core dumped
- References: <op dot wzfrolroofd6j1 at nebbiolo dot upc dot de> <51CEC839 dot 507 at cornell dot edu> <op dot wzfwtr0wofd6j1 at nebbiolo dot upc dot de> <51CEE558 dot 6070104 at cornell dot edu> <op dot wzgaely4ofd6j1 at nebbiolo dot upc dot de> <51CF2925 dot 2060804 at cornell dot edu> <op dot wzggt0qzofd6j1 at nebbiolo dot upc dot de>
On 6/29/2013 3:38 PM, Helmut Karlowski wrote:
Ken Brown, 29.06.2013 20:36:21:
setup.ini just lists available packages. Use cygcheck to find out
what you have actually installed.
When a package is installed it also lists something like:
No. setup.ini lists the packages that are available for install. Often
there is a "previous" version as well as a "current" version. This
allows you to choose, when running setup.exe, the previous version if
you don't want to install the current version for some reason.
Occasionally there is also a test version. None of this has anything to
do with which packages you have installed.
dvipdfm.def no longer exists in TeX Live 2013, and you shouldn't have
to create it. Please give the details of what you were doing that led
to this error message.
1. pdfetex -progname latex $*
2. dvipdfm -p a4 $*
I just tried these commands with no problems:
$ pdfetex -progname latex sample2e.tex
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Cygwin)
restricted \write18 enabled.
entering extended mode
Babel <3.9f> and hyphenation patterns for 78 languages loaded.
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/omscmr.fd)   
Output written on sample2e.dvi (3 pages, 7484 bytes).
Transcript written on sample2e.log.
$ dvipdfm -p a4 sample2e
sample2e.dvi -> sample2e.pdf
32208 bytes written
including the part about attaching cygcheck output.
If you read it, you'll see near the end which packages you have installed.
The one suspicious thing that I see is your path. For example, the
cygcheck output includes
Warning: C:\bin\awk.exe hides C:\cygwin\bin\awk
Could there be other things in C:\bin or C:\cygwin\opt\cross-mint\bin
that are interfering with Cygwin?
Anyway I'm interested in the crashes in the first place.
Sorry, I can't help you with that.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple