From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-developers@cygwin.com
Subject: Re: Failure during build of Python 3.8 via cygport
Date: Tue, 15 Dec 2020 09:52:17 +0100 [thread overview]
Message-ID: <5af26d10-592e-657a-7817-ea267baa883c@gmail.com> (raw)
In-Reply-To: <e4e305cf-a5e4-a8c1-de22-59575600e987@maxrnd.com>
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 ?
next prev parent reply other threads:[~2020-12-15 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a7bcec5f-b01b-c1e4-81e6-1990f11e351e@maxrnd.com>
[not found] ` <Pine.BSF.4.63.2012112223120.53260@m0.truegem.net>
[not found] ` <758d2138-587b-2970-6c35-69d5c655a598@maxrnd.com>
2020-12-14 10:42 ` Mark Geisert
2020-12-14 11:33 ` Corinna Vinschen
2020-12-15 8:06 ` Mark Geisert
2020-12-15 8:52 ` Marco Atzeri [this message]
2020-12-15 9:07 ` Mark Geisert
2020-12-15 12:06 ` Corinna Vinschen
2020-12-15 12:14 ` Corinna Vinschen
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=5af26d10-592e-657a-7817-ea267baa883c@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-developers@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).