From: Mark Geisert <mark@maxrnd.com>
To: Cygwin-Apps <cygwin-apps@cygwin.com>
Subject: Failure during build of Python 3.8 via cygport
Date: Wed, 9 Dec 2020 00:14:07 -0800 [thread overview]
Message-ID: <a7bcec5f-b01b-c1e4-81e6-1990f11e351e@maxrnd.com> (raw)
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" ; \
> rm -f ./pybuilddir.txt ; \
> exit 1 ; \
> fi
> Traceback (most recent call last):
> File "/usr/src/python38-3.8.3-1.src/python38-3.8.3-1.x86_64/src/Python-3.8.3/Lib/runpy.py", line 194, in _run_module_as_main
> return _run_code(code, main_globals, None,
> File "/usr/src/python38-3.8.3-1.src/python38-3.8.3-1.x86_64/src/Python-3.8.3/Lib/runpy.py", line 87, in _run_code
> exec(code, run_globals)
> File "/usr/src/python38-3.8.3-1.src/python38-3.8.3-1.x86_64/src/Python-3.8.3/Lib/sysconfig.py", line 711, in <module>
> _main()
> File "/usr/src/python38-3.8.3-1.src/python38-3.8.3-1.x86_64/src/Python-3.8.3/Lib/sysconfig.py", line 699, in _main
> _generate_posix_vars()
> File "/usr/src/python38-3.8.3-1.src/python38-3.8.3-1.x86_64/src/Python-3.8.3/Lib/sysconfig.py", line 416, in _generate_posix_vars
> f.write(pybuilddir)
> UnicodeEncodeError: 'utf-8' codec can't encode characters in position 17-19: surrogates not allowed
> generate-posix-vars failed
> make: *** [Makefile:592: pybuilddir.txt] Error 1
> *** ERROR: make failed
I've seen UnicodeEncodeError before and searched and found how to fix it.. but
hitting the issue while building Python itself seems more fraught. Is this a
known issue with known fix?
Thank you,
..mark
next reply other threads:[~2020-12-09 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 8:14 Mark Geisert [this message]
2020-12-12 6:33 ` Mark Geisert
2020-12-13 8:52 ` Mark Geisert
2020-12-13 14:34 ` Marco Atzeri
2020-12-13 21:59 ` Brian Inglis
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=a7bcec5f-b01b-c1e4-81e6-1990f11e351e@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-apps@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).