From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Building python*-docutils
Date: Mon, 24 Jul 2017 12:34:00 -0000 [thread overview]
Message-ID: <505423d2-0a2d-a574-2ce2-cea0e7b19d6c@cornell.edu> (raw)
In-Reply-To: <bfc27360-0c48-1865-f69a-1c7e22002795@cygwin.com>
On 7/23/2017 10:59 PM, Yaakov Selkowitz wrote:
> On 2017-07-23 13:17, Ken Brown wrote:
>> I tried to reproduce the build of python*-docutils, and the build fails
>> as follows:
>>
>> error: invalid command 'bdist_wheel'
>>
>> 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.
>
> You're probably not using cygport git master:
>
> https://github.com/cygwinports/cygport/commit/f44b055a79e6db57cd10d6782e17f93fd460aae3
That was it. Thanks.
Ken
prev parent reply other threads:[~2017-07-24 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 18:17 Ken Brown
2017-07-24 2:59 ` Yaakov Selkowitz
2017-07-24 12:34 ` Ken Brown [this message]
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=505423d2-0a2d-a574-2ce2-cea0e7b19d6c@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).