From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Python extraneous dependencies
Date: Tue, 26 Mar 2019 18:25:00 -0000 [thread overview]
Message-ID: <5c9a6eac.1c69fb81.cd67b.94ca@mx.google.com> (raw)
In-Reply-To: <3dc5b19f876e7fa109e7e61dea8463ce748630eb.camel@cygwin.com>
On Tue, 26 Mar 2019 10:08:27, Yaakov Selkowitz wrote:
>> It seems that function doesnt even work:
>>
>> $ python3.6 -q
>> > > > from ctypes.util import find_library
>> > > > print(find_library('z'))
>> None
>
> WFM (returns cygz.dll), do you have the respective -devel packages
> installed? Those are also required for find_library.
still failing for me after installing "python36-devel". however even if it
works, it seems we have an issue. if you need "python36-devel" to use
"find_library", then it seems you only need "binutils" if you are installing
"python36-devel", not "python36".
so the "binutils" dep should be moved from "python36" to "python36-devel". this
way it only hurts people installing the development python, not also people
wanting to run "print('hello world')"
if you have another reason why "python36" should require "binutils" i would be
interested to read it - thanks.
--
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:[~2019-03-26 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 1:45 Steven Penny
2019-02-24 3:08 ` LRN
2019-02-25 2:24 ` Yaakov Selkowitz
2019-02-25 13:54 ` Steven Penny
2019-02-26 5:31 ` Yaakov Selkowitz
2019-02-26 9:48 ` Ray Donnelly
2019-03-26 2:39 ` Steven Penny
2019-03-26 14:08 ` Yaakov Selkowitz
2019-03-26 18:25 ` Steven Penny [this message]
2019-03-26 18:58 ` Yaakov Selkowitz
2019-03-26 23:09 ` Steven Penny
2019-04-21 15:46 ` Steven Penny
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=5c9a6eac.1c69fb81.cd67b.94ca@mx.google.com \
--to=svnpenn@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).