Fix: Add -m64 linker flag for ibm-openxl on z/OS#408
Open
KiarashIBM wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When using
ibm-clang(without the 64 suffix) to build Python packages on z/OS, setuptools fails to build C extensions with AMODE mismatch errors. The compiler correctly adds-m64during compilation to target 64-bit mode, but the linker was missing this flag, causing 31-bit/64-bit linking errors.Solution
Add
-m64to the linker flags foribm-openxlcompilers indistutils/compilers/C/zos.pyto match the compilation flags and ensure consistent 64-bit mode throughout the build process.Testing
Tested with both
ibm-clangandibm-clang64compilers on z/OS. C extensions now build successfully without AMODE errors.Fixes: Issue #407