-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-31904 : Python should support VxWorks RTOS #4179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -2314,17 +2321,17 @@ cmsg_min_space(struct msghdr *msg, struct cmsghdr *cmsgh, size_t space) | |||
#endif | |||
if (msg->msg_controllen < 0) | |||
return 0; | |||
if (space < cmsg_len_end) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is mistake will have recall the pull request and move this back where it was orignally
configure
Outdated
@@ -2927,7 +2927,7 @@ $as_echo_n "checking for python interpreter for cross build... " >&6; } | |||
if $interp -c "import sys;sys.exit(not '.'.join(str(n) for n in sys.version_info[:2]) == '$PACKAGE_VERSION')"; then | |||
break | |||
fi | |||
interp= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could restore this?
But I'm not sure it's necessary?
Do you automatically rewrite ./configure and check in ./configure.ac has changed, or do I need to supply it in my pull?
If I do need to provide an updated ./configure in the pull, do I have to use a specific version of autotools ( I notice this one is a bit dated ?)
@@ -1995,14 +2034,15 @@ def detect_ctypes(self, inc_dirs, lib_dirs): | |||
|
|||
ext = Extension('_ctypes', | |||
include_dirs=include_dirs, | |||
extra_compile_args=extra_compile_args, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to be restored
All doesn't include shared if static build Hardwire asscii encoding for VxWorks default to UTF-8 (like Android) Semicolon as path separator If build is configure'd for static, propigate to Makefile Add detection for oddly named VxWorks OPENSSL and HASH libraries Fix some warnings with unused functions and macro re-def Extra include in faulthandler.c Avoid duplicate macro definition Setup.py complies all VxWorks compatible modules Update some extension modules to compile on VxWorks VxWorks does not have "timezone" and daylight "constants" Limited signal fields in VxWorks undef DATE TIME for VxWorks
# Conflicts: # setup.py
This pull request enables cpython to cross-build on VxWorks (the world’s leading RTOS and the only interplanetary OS)
This does not provide complete configuration of all target systems possible. It's assumed that the user is familiar with automake cross-builds and has called ./configure with the appropriate environment (CFLAGS,LDFLAGS, CC,CCP, etc) and appropriate site.config and configuration arguments.
VxWorks 7 currently supports Intel, ARM and PowerPC processors running in 32bit and 64bit mode compiled with GCC, ICC, a llvm/clang variant, or Wind River’s Diab compiler. So the verification matrix is large and subsequent pull requests will address the various variants as they are validated.
This pull also also includes some support for automake's --enable-shared=no functionality. If this non-default flag is set, various targets and flags are disabled in Make.pre.in and thus the generated Makefile
Validated with GCC 4.8.1.10 as provided with VxWorks 7
.. and an appropriate site.config
https://bugs.python.org/issue31904