-
Notifications
You must be signed in to change notification settings - Fork 17
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
manywheel linux shared object issue #14
Comments
From http://www.verycomputer.com/183_d2c8799a512b77ba_1.htm > The problem apparently is due > to the fact that libf2c.a/so has a main object included which expects > a resolution of the symbol MAIN__ that is ostensibly provided by f2c > when a fortran PROGRAM is compiled under it. > The simplest and most logical > solution to the problem is to pass the argument '-u MAIN__' to the > linker which allows the symbol to go unresolved.
Ok this one was a freaking nightmare, but I think it's now working! The issue is a very weird one, in that I had previously gotten around this by adding a simple The thing that worked was linking against To make matters more complicated, CentOS used in the manylinux docker container does not include It looks like the |
It turns out that the manywheels linux build stopped complaining about MAIN__, but segfaulted when you tried to use the ne21c.so 😢 It also seems that auditwheel doesn't copy over the libf2c.a that is required. I reverted to trying to use the However, the wheel is still broken. I now find that even if I compile libf2c from source, or use the
I think there's something fundamentally wrong with |
Any solution to this? I run Fedora and have the same error. |
Unfortunately not, I'd suggest trying the f2c in conda ( |
the generate-wheels.yml github action is missing something:
That symbol is in the ne21c
main.cpp
, unsure what libf2c thinks its doing... This one might take a while to debug. For now I have deleted from PyPi the broken wheels.The text was updated successfully, but these errors were encountered: