From: airplanemath <airplanemath@aol.com>
To: cygwin@cygwin.com
Subject: Re: Possible xpdf packaging error?
Date: Thu, 07 Apr 2022 11:13:46 -0400 [thread overview]
Message-ID: <vriuzgkx53kl.fsf@mail.aol.com> (raw)
In-Reply-To: <7189c830-c11f-7320-ffcc-4a45db11fd54@cs.umass.edu>
On Thu, Apr 07 2022, Eliot Moss wrote:
> Dear Cygwin-ers --
>
> Today I had use for pdftotext. It man page is installed, but the program
> itself is missing. On Ubuntu (etc.) it is part of the xpdf package, the
> Cygwin version of which I have installed. pdftotext.cc is in the source
> package, but its executable is not present in the binary package.
>
$ cygcheck -p bin/pdftotext
Found 6 matches for bin/pdftotext
poppler-debuginfo-0.88.0-1 - poppler-debuginfo: Debug info for poppler
poppler-debuginfo-0.88.0-2 - poppler-debuginfo: Debug info for poppler
poppler-debuginfo-21.01.0-1 - poppler-debuginfo: Debug info for poppler
poppler-0.88.0-1 - poppler: PDF manipulation utilities
poppler-0.88.0-2 - poppler: PDF manipulation utilities
poppler-21.01.0-1 - poppler: PDF manipulation utilities
Try installing poppler
> So I am wondering if this is intentional (is pdftotext somewhere else?) or an
> oversight. The situation seems the same from at least the 4.01.01 release
> onward to 4.03 (current) release.
This looks to be intentional, given the mention in the last several
announcements, e.g.
https://cygwin.com/pipermail/cygwin-announce/2021-February/009922.html
>
> I suppose I can try getting all the necessary dependencies and building from
> source, if need be, but though this worth asking about.
>
> Regards - Eliot Moss
Other ways to check are cygcheck -p pdftotext.exe or
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=bin%2Fpdftotext&arch=x86_64,
next prev parent reply other threads:[~2022-04-07 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:28 Eliot Moss
2022-04-07 15:13 ` airplanemath [this message]
2022-04-07 19:03 ` Eliot Moss
2022-04-07 19:18 ` 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=vriuzgkx53kl.fsf@mail.aol.com \
--to=airplanemath@aol.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).