From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Building python*-docutils
Date: Sun, 23 Jul 2017 18:17:00 -0000 [thread overview]
Message-ID: <3da6f201-b106-e4d4-33c8-e2dba8a5fd68@cornell.edu> (raw)
Yaakov,
I tried to reproduce the build of python*-docutils, and the build fails
as follows:
$ cygport python-docutils.cygport prep compile
>>> Preparing python-docutils-0.13.1-2.noarch
>>> Unpacking source docutils-0.13.1.tar.gz
>>> Preparing working source directory
>>> Compiling python-docutils-0.13.1-2.noarch
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
*** ERROR: setup.py bdist_wheel failed
Is there a patch that was inadvertently omitted from the source package?
Or is there some unusual build dependency for this package? I've
successfully built several other python packages that inherit
python-wheel, so I don't think there's anything wrong with my build
environment.
Thanks.
Ken
next reply other threads:[~2017-07-23 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 18:17 Ken Brown [this message]
2017-07-24 2:59 ` Yaakov Selkowitz
2017-07-24 12:34 ` 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=3da6f201-b106-e4d4-33c8-e2dba8a5fd68@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).