Re: Failure during build of Python 3.8 via cygport

2020-12-13 Thread Brian Inglis
On 2020-12-13 07:34, Marco Atzeri via Cygwin-apps wrote: 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 someho

Re: Failure during build of Python 3.8 via cygport

2020-12-13 Thread Marco Atzeri via Cygwin-apps
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, buil

Re: Failure during build of Python 3.8 via cygport

2020-12-13 Thread Mark Geisert
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.c

Re: Failure during build of Python 3.8 via cygport

2020-12-11 Thread Mark Geisert
[replying to myself again...] A similar problem happens when building 3.6 and 3.7 too. Details at end. On Wed, 9 Dec 2020, Mark Geisert wrote: Hi Marco, I was building Python locally so I can later submit a patch against it. It appears the local python.exe was built successfully, but a later

Failure during build of Python 3.8 via cygport

2020-12-09 Thread Mark Geisert
Hi Marco, I was building Python locally so I can later submit a patch against it. It appears the local python.exe was built successfully, but a later step failed with: ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ if test $? -ne 0 ; then \ echo "generate-posix-vars failed"