From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83306 invoked by alias); 4 Sep 2016 19:43:55 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 83295 invoked by uid 89); 4 Sep 2016 19:43:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*i:sk:19afd29, H*f:sk:19afd29, H*MI:sk:19afd29, research X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 04 Sep 2016 19:43:53 +0000 Received: from [192.168.0.3] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id CB4B540470C0; Sun, 4 Sep 2016 15:43:51 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Problem with Python programs with binary components, who to blame? References: <156f59f4272.c6a11ec33673.3924353846235894325@zoho.com> <19afd29b-3fbb-922f-9b05-e394475f1876@gmail.com> To: cygwin@cygwin.com From: Eliot Moss Message-ID: Date: Sun, 04 Sep 2016 19:43:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <19afd29b-3fbb-922f-9b05-e394475f1876@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00073.txt.bz2 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