From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Problem with Python programs with binary components, who to blame?
Date: Sun, 04 Sep 2016 19:43:00 -0000 [thread overview]
Message-ID: <f4bea7c8-0e92-ed2e-86a0-0210d02d29db@cs.umass.edu> (raw)
In-Reply-To: <19afd29b-3fbb-922f-9b05-e394475f1876@gmail.com>
On 9/4/2016 10:43 AM, Marco Atzeri wrote:
> On 04/09/2016 16:34, Patrick Pief wrote:
>> Hi,
>>
>> 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?
>
>
> On windows all symbols must be available at linking time.
> Cygwin programs/libraries have the same constrain.
>
> Can you report the full command that produce :
> ""relocation truncated to fit [...] against undefined symbol"." ?
>
> Are you building a specific program or it is your own development ?
I also wonder about:
- 32-bit versus 64-bit Cygwin, whether it may be an issue
- Such a build would need to be treated as a Posix build,
not a Windows build, and probably should not be trying to
access Windows libraries (as opposed to Cygwin libraries)
dllimport is meaningful for Windows, not for Posix, I believe.
So I wonder if you're actually running Cygwin's gcc ...
Anyway, some things to check into ...
Eliot Moss
--
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 19:43 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 [this message]
2016-09-04 20:34 ` Brian Inglis
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=f4bea7c8-0e92-ed2e-86a0-0210d02d29db@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).