You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2021-10-20.12:42:30.091>created_at=<Date2013-03-31.19:43:30.946>labels= ['type-feature', 'build']
title='mingw: configure MACHDEP and platform for build'updated_at=<Date2021-10-20.12:42:30.090>user='https://bugs.python.org/rpetrov'
There are some spelling errors in the comments. It would also be good to keep the indentation, quoting, layout etc similar to the surrounding code.
Regarding the comments, what is the significance of “runtime platform” vs MACHDEP? Also, what is the significance of sys.platform() when setting _PYTHON_HOST_PLATFORM?
Why did you use different types of comments? (# vs dnl)
I do not understand the comment “build must not depend from posix-compatible environment”. Is this just explaining that we are setting ac_sys_system (uname -s) to a dummy generic value that will not trigger any special cases. Should we also set ac_sys_release to an empty string, like the cross-compiling case later on?
What’s the go with the two competing “mingw*)” cases when determining _PYTHON_HOST_PLATFORM? What is the situation where $host matches *--mingw, but $host_os does not match mingw*?
Here is a modified patch fixing a couple of the spelling & style problems. I moved the comment introducing the ac_sys_ variables up to before the code that sets them. I rearranged the logic for _PYTHON_HOST_PLATFORM so it is clear that $host_os overrides $host, and I combined the cygwin and mingw cases.
I suspect the configure.ac logic could be simplified more.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: