From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] python-sphinx 1.6.5-1
Date: Fri, 01 Dec 2017 16:50:00 -0000 [thread overview]
Message-ID: <7d46925b-dbec-8b10-6120-4157719c2c3f@cygwin.com> (raw)
In-Reply-To: <CAKf2h5QKeYCrs41Os4+pTp0-FtMEMDDD3gwgfd8Q7C5Y0kwMdA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 954 bytes --]
On 2017-12-01 08:05, Frank Fesevur wrote:
> $ make html
> Makefile:12: *** The 'sphinx-build' command was not found. Make sure
> you have Sphinx installed, then set the SPHINXBUILD environment
> variable to point to the full path of the 'sphinx-build' executable.
> Alternatively you can add the directory with the executable to your
> PATH. If you don't have Sphinx installed, grab it from
> http://sphinx-doc.org/. Stop.
>
> I tried to reinstall the python2-sphinx package from setup.exe but
> without any success.
>
> Indeed, in /bin there is no sphinx-build or sphinx-quickstart.
Like our other current Python packages, the binaries are now in the
python3 package:
$ cygcheck -p sphinx-build
Found 2 matches for sphinx-build
python-sphinx-1.2.3-1 - python-sphinx: Python documentation generator
(installed binaries and support files)
python3-sphinx-1.6.5-1 - python3-sphinx: Python documentation generator
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2017-12-01 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a1bb48d.0c666b0a.286e1.0895SMTPIN_ADDED_MISSING@mx.google.com>
2017-12-01 14:05 ` Frank Fesevur
2017-12-01 16:50 ` Yaakov Selkowitz [this message]
[not found] <31198.1789571748$1511765134@news.gmane.org>
2017-11-30 16:55 ` René Berber
2017-11-27 6:44 Yaakov Selkowitz
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=7d46925b-dbec-8b10-6120-4157719c2c3f@cygwin.com \
--to=yselkowitz@cygwin.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).