Aaron Hurst added the comment:
I believe this bug can be closed now that the following have landed:
New changeset 408a2ef1aceff1f4270c44552fa39ef93d9283e3 by Benjamin Peterson
(aaronpaulhurst) in branch 'master':
closes bpo-35184: Fix XML_POOR_ENTROPY option that breaks makesetup
Change by Aaron Hurst :
--
keywords: +patch
pull_requests: +12827
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35184>
___
___
Py
Aaron Hurst added the comment:
I can reproduce this issue by uncommenting the pyexpat line in Setup.dist and
compiling.
The issue is with -DXML_POOR_ENTROPY=1. The equals character causes the line
to be incorrectly interpreted as a macro definition by makesetup. This results
in an
Aaron Hurst added the comment:
This is the same issue as https://bugs.python.org/issue35184
I can reproduce this issue by uncommenting the pyexpat line in Setup.dist and
compiling.
The issue is with -DXML_POOR_ENTROPY=1. The equals character causes the line
to be incorrectly interpreted
Change by Aaron Hurst :
--
pull_requests: +12981
___
Python tracker
<https://bugs.python.org/issue35184>
___
___
Python-bugs-list mailing list
Unsubscribe:
Aaron Hurst added the comment:
Sorry for my misunderstanding of the process, and thanks for explaining. I
resubmitted the PR against the master branch.
--
___
Python tracker
<https://bugs.python.org/issue35
Aaron Hurst added the comment:
Hi Ned,
>From a fresh checkout of master on Ubuntu 18.04, I uncomment the pyexpat line
>in Modules/Setup and run:
cpython$ ./configure
...
cpython$ make
Makefile:273: *** missing separator. Stop.
Here is the offending section of the resulting Makefile
Aaron Hurst added the comment:
Hi Ned,
Thanks for testing this. I also observe that macOS compiles "without error"...
but it's still broken... and silently.
This is because the pyexpat line isn't being turned into the expected set of
source compilation rules, but
