From: "Sven Köhler" <sven.koehler@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: TeX Live 2012
Date: Tue, 17 Jul 2012 16:14:00 -0000 [thread overview]
Message-ID: <ju42vc$mm8$1@dough.gmane.org> (raw)
In-Reply-To: <5004D6FE.2080107@cornell.edu>
Am 17.07.2012 05:07, schrieb Ken Brown:
> On 7/16/2012 6:48 PM, Sven Köhler wrote:
>> Am 16.07.2012 13:39, schrieb Ken Brown:
>>> Cygwin's TeX Live packages have been updated to the latest upstream
>>> release, TeX Live 2012.
>>
>> Just updated cygwin inside my Windows 7 virtual machine. It's not
>> looking good. The following kind of generic error shows in mintty:
>>
>> -bash: /usr/bin/pdflatex: Bad address
>
> Have you tried rebaseall?
Sure.
> If that doesn't help, please make a full
> problem report, following the guidelines at
>
> http://cygwin.com/problems.html
I wonder, whether it would have helped. But the mystery is solved now,
even though another mystery remains. Long story short:
1) "Bad address" is just a very confusing error message
2) There's a packaging error, namely that pdftex.exe depends on
cygpoppler-26.dll, but the texlive packages don't depend on the
libpoppler26 package.
Please fix 2).
What about 1)? Is this a known problem, that cygwin reports "Bad
address" when a DLL cannot be found? Shouldn't cygwin print a more more
comprehensive error message like "cygpoppler-26.dll not found"?
Regards,
Sven
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-17 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 12:16 Ken Brown
2012-07-16 14:01 ` Nellis, Kenneth
2012-07-16 16:26 ` Ken Brown
2012-07-16 19:02 ` Nellis, Kenneth
2012-07-16 19:23 ` Ken Brown
2012-07-16 22:44 ` Sven Köhler
2012-07-17 3:08 ` Ken Brown
2012-07-17 16:14 ` Sven Köhler [this message]
2012-07-17 18:08 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ju42vc$mm8$1@dough.gmane.org' \
--to=sven.koehler@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).