public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Numpy 1.12.1 setup issue (targetting Python 3.6.1) from Cygwin 2.8.0
Date: Sun, 16 Apr 2017 19:03:00 -0000	[thread overview]
Message-ID: <c121be04-b63e-2854-689f-7888c0c42fa5@cs.umass.edu> (raw)
In-Reply-To: <1492342647795-133490.post@n5.nabble.com>

On 4/16/2017 7:37 AM, Kptain wrote:
> Yes, but as I said, the problem is this step was already done:
> 
> "I would add that python3-numpy package was added when I have selected
> cygwin package for setup".
> 
> For me the problem is to identify clearly other cygwin packages required as
> dependencies are not already highlighted by cygwin setup.
> 
> Concerning Python3 packages installed, PIP is done for that and is working
> well.
> I have already used for Py packages used pure python source code: no
> problem.
> 
> However for Py libraries involving C source code or having some graphics
> dependencies, the problem is different: it is exactly the issue I'm facing
> with numpy.
> I could have added same kind of issue with matplotlib.

I am sure someone else will correct me if I am wrong, but you
need the Cygwin versions of these, not the Windows or Linux
versions.  I suspect PIP does not fetch Cygwin versions, thus
you must acquire these via setup.  However, they are not
required for base python, so you have to request them explicitly
in setup ...

An alternative is to build them from source yourself under Cygwin,
which I seem to recall doing at some point ...

Regards -- EM

--
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

  reply	other threads:[~2017-04-16 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 12:44 Kptain
2017-04-16 18:22 ` Marco Atzeri
2017-04-16 18:24 ` Kptain
2017-04-16 19:03   ` Eliot Moss [this message]
2017-04-17 17:59     ` Kptain
2017-04-25 18:07       ` Erik Bray
2017-04-26  1:51         ` Eliot Moss
2017-04-26  8:19           ` Brian Inglis
2017-04-26  9:20             ` Eliot Moss
2017-04-26 15:21             ` Kptain

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=c121be04-b63e-2854-689f-7888c0c42fa5@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).