From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Problem with Python programs with binary components, who to blame?
Date: Sun, 04 Sep 2016 20:34:00 -0000 [thread overview]
Message-ID: <208ad79b-35dd-0d71-4949-3fc51c4bf044@SystematicSw.ab.ca> (raw)
In-Reply-To: <156f59f4272.c6a11ec33673.3924353846235894325@zoho.com>
On 2016-09-04 08:34, Patrick Pief wrote:
> Before writing any formal bug report I thought I might ask first whether the
> problem I am seeing is something that can be even fixed from Cygwin's side.
> The issue has to do with the compilation of Python binary packages for Python
> inside Cygwin (Python installed as a Cygwin package as opposed to Python for
> Windows).
> The problem starts to show as gcc warnings: "[â¦] redeclared without dllimport
> attribute: previous dllimport ignored", and ends with linkers errors such as:
> "relocation truncated to fit [...] against undefined symbol".
> I am guessing the problem might actually lie within the Python sources itself
> but I am not entirely sure.
> So is this some issue that is even worth further research and filing a bug
> report here?
Hi Patrick,
Read about cygwin dll exports and imports at
https://cygwin.com/cygwin-ug-net/dll.html
You may want to find a similar Cygwin Python module and look at the source
package (something called python-...-v.n-p-src) to see how it is built using
cygport, which takes care of some Cygwin specific differences in builds.
If you still have issues, please provide all the information requested by:
https://cygwin.com/problems.html
which includes attaching cygcheck and build output logs.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2016-09-04 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 14:34 Patrick Pief
2016-09-04 14:43 ` Marco Atzeri
2016-09-04 19:43 ` Eliot Moss
2016-09-04 20:34 ` Brian Inglis [this message]
2016-09-05 4:50 ` Doug Henderson
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=208ad79b-35dd-0d71-4949-3fc51c4bf044@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).