From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by sourceware.org (Postfix) with ESMTPS id A2327385800E for ; Sun, 13 Dec 2020 14:34:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A2327385800E Received: by mail-wm1-x32e.google.com with SMTP id a6so11484945wmc.2 for ; Sun, 13 Dec 2020 06:34:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=MNK+oKpPNzuE9fG0ER7xEfp42g6udZuUmD2Tgi41vEg=; b=C1HlrZXvDoSn0RwJG2eyx1Mcf0UT0DARIJZnZmPwastdc8OZKFuxbgIqEqWuuENj3C Z1n6vLpDZ1ALAJ1Mr706xLIM/FXRGLlkIK9M/e14t80TRgioslBBemmnV0QMJdGAd7Zn q0weT5lLv7usBoDUg0XKkK2p8vSmuVtCNFVjeNBE1MvX2s86Me+zyiK22dIdkz0yXzG6 +ageQoj5I3hiDCG9/NK50eqbJXCkTEaPK38MT7Kx2J7EbLD/7wkitqGWmkFzdQ5GEtg7 AfAN3qq7Z5e2kynFEqc08La/EIEKuBeF1URToYgcGMwNvyuMwPzqra35oMP82Zdct4ra xNbw== X-Gm-Message-State: AOAM531hb5PRkkKUk9xqW59TZ8EFoOW0YnTdSV7c14QQwst+afh6wagB dRZqzOdfzw3g3aQ2pG15oX4MCgfHltM= X-Google-Smtp-Source: ABdhPJzrzvIYg3NqVvJMSd0WJ3ZFGpnuZzoKOeOSIgYkd3T/Ybg67iketWJCPB5RBHBvyoe2PfuTaw== X-Received: by 2002:a1c:287:: with SMTP id 129mr23583137wmc.133.1607870093726; Sun, 13 Dec 2020 06:34:53 -0800 (PST) Received: from ?IPv6:2003:cc:9f10:5823:cdbf:5de7:a83c:7ac5? (p200300cc9f105823cdbf5de7a83c7ac5.dip0.t-ipconnect.de. [2003:cc:9f10:5823:cdbf:5de7:a83c:7ac5]) by smtp.gmail.com with ESMTPSA id v1sm25564163wrr.48.2020.12.13.06.34.52 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 13 Dec 2020 06:34:53 -0800 (PST) Subject: Re: Failure during build of Python 3.8 via cygport To: cygwin-apps@cygwin.com References: <758d2138-587b-2970-6c35-69d5c655a598@maxrnd.com> From: Marco Atzeri Message-ID: <1fea201e-4787-4d58-f809-07613c3f73fa@gmail.com> Date: Sun, 13 Dec 2020 15:34:51 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <758d2138-587b-2970-6c35-69d5c655a598@maxrnd.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 14:34:56 -0000 On 13.12.2020 09:52, Mark Geisert wrote: > Mark Geisert wrote: >> This seems to be a problem setting up a platform-specific build >> directory. The sysconfig.py script wants to use "lib." + platform + >> pythonversion but the platform string somehow gets corrupted into >> non-utf8 bytes.  For instance, building Python 3.8 comes up with: >>      lib.cygwin-\365\377\377o-\377o-3.8 >> as the directory name.  Broken, but could work.  The build failure >> happens because the script tries to write this directory name into a >> file but it's not a valid utf8 string.  The directory name should have >> been: >>      lib.cygwin-3.2.0-x86_64-3.8 > > And the corruption is due to something about a recent change to the > operation of Cygwin's uname() function.  The change was introduced in > Cygwin API version 335; I'm running 340 on my test machine.  This being > a fairly recent change might possibly explain why nobody else has run > into this issue yet. > > Basically, os.uname within Python is calling Cygwin's uname() passing > the address of a buffer declared to be 'struct utsname'.  The structure > layout changed in API 335.  What I've hit is a mismatch between what > Python expects and Cygwin delivers. > > I'll move this discussion over to the developers list tomorrow. > > ..mark thanks for the analysis let me know if you think we should correct the python build in any way Regards Marco