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
_sysconfigdata.py is installed in an arch-independent directory #62283
Comments
_sysconfigdata.py is installed into ${prefix}/lib/pythonX.Y/_sysconfigdata.py which is an architecture-independent directory, as opposed to a path starting with e.g. ${libdir}, which is architecture-dependent. But _sysconfigdata.py contains architecture-dependent information, which breaks some installation, specifically Solaris multi-arch. A fix would be to move it to an architecture-dependent directory, but this probably requires some discussion. ----------------------------------------------------------------------- Original question on the mailing list: I'm looking into creating a 32/64-bit Python (2.x and/or 3.x) package There currently is a Python package that I maintain, which is 32-bit only[2]. I have made an attempt to build a 64-bit package, and my findings are Ideally, I'd make _sysconfigdata.py return/set different values if we're 64-bit:
set values for the 64-bit platform
else:
set values for the 32-bit platform It's a similar approach to how we currently handle C header files. See The problem is that it would involve somewhat intrusive patching of |
Did Solaris adopt MultiArch? ;-P Nice! So what I did for the Debian and Ubuntu builds is:
Note that IN.py is another architecture dependent file which differs at least on several linux architectures. |
bpo-23968 moves _sysconfigdata.py to an arch dependent directory |
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: