-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: pandas does not build on AIX - when using xlc/xlC as compiler #35123
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
Comments
we have no support on AIX - but would accept patches |
Would love to help - but will need help creating a patch. Cython says - not our problem: cython/cython#3723 The pandas reference they include goes well beyond my understanding of compilers. Maybe it is fixed in v16 of the IBM compiler (I have v11 licensed), maybe it will be fixed in the next release (based on LLVM iirc) - but that does not help me now. And switching to gcc is not a supportable option for me. For AIX, using gcc means you must develop and maintain a complete GNU-GCC RTE. Do not have the resources for that. |
For a starting point - currently testing the tagged
FYI: checked my archives - last version I had built successfully was 0.19.0 (in Oct 2106) |
I think @da-woods summed it up well on the Cython issue; seems like more of a compiler C++11 support issue than anything else If you can find a way to define compatible functions without C++11 support feel free to push a PR |
At this point in time pandas requires C++11 and that is explicitly enforced by the build system, so I don't think there is much to do here |
[x ] I have checked that this issue has not already been reported.
[ x] I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
Panda build stops with:
On examining this I see that there are special statements - perhaps unsupported by xlc/xlC (v11).
There is a good chance this is an issue caused by cython. but I thought I would post/mention it here as well.
The text was updated successfully, but these errors were encountered: