From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 1D6D8385800D for ; Tue, 15 Dec 2020 09:07:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1D6D8385800D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=mark@maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 0BF97gEs075339 for ; Tue, 15 Dec 2020 01:07:42 -0800 (PST) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpduifOQU; Tue Dec 15 01:07:34 2020 Subject: Re: Failure during build of Python 3.8 via cygport To: cygwin-developers@cygwin.com References: <758d2138-587b-2970-6c35-69d5c655a598@maxrnd.com> <0f498c92-409b-6ac8-d0ba-93ac753ab4b8@maxrnd.com> <20201214113300.GA4560@calimero.vinschen.de> <5af26d10-592e-657a-7817-ea267baa883c@gmail.com> From: Mark Geisert Message-ID: Date: Tue, 15 Dec 2020 01:07:34 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <5af26d10-592e-657a-7817-ea267baa883c@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 09:07:44 -0000 Marco Atzeri via Cygwin-developers wrote: > On 15.12.2020 09:06, Mark Geisert wrote: >> Hi Corinna, >> >> Corinna Vinschen via Cygwin-developers wrote: >>> On Dec 14 02:42, Mark Geisert wrote: >> [...] >>> >>> In retrospect, uname_x should be named _uname_x or so, with a leading >>> underscore, so as not to pollute the namespace, but either way, that >>> isn;t your problem. >> >> OK, I see. >> >>> The problem here might be that you get the old uname function if >>> you dlopen the cygwin dll and dlsym(hdl, "uname").  Is that the >>> case in python? >> >> Yes it is. >> >>> If so, I have a simple, dirty workaround below.  Can you check if that's >>> the problem, please? >> >> A new Cygwin DLL built with your patch does correct this 'uname' issue when >> building Python.  Wonderful! >> Thank you very much! >> >> ..mark > > It seems I do not need to rebuild python for this reason. Correct ? That's correct Marco. But it allows me to build Python locally so I can produce patch(es) for the test_asyncore.py issue involving AF_UNIX sockets. When I've got a patch I'll follow up on the cygwin-apps list, I guess. Thanks for keeping an eye on this. ..mark