-
Notifications
You must be signed in to change notification settings - Fork 59
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
0.9.1 and newer generate IDs that require -Wl,-headerpad_max_install_names #147
Comments
I can't find much info on this. How the library is built might be affected by your version of Xcode, so see if you can update that and rebuild. If |
I don't think it's my compiler version. The libraries that I built myself get processed by delocate-wheel with no fuss. I don't have any control at all over how I could theoretically work around this by building Boost from source myself, but that involves a major revamp of my CI pipeline. Also, there's a lifetime limit on how many times a body can build Boost from source before the universe collapses, and I'm pushing it as it is... Is it possible to find out how much room for install_name changes is available in any particular binary? Is it possible to have delocate generate shorter names? |
Bug: delocate-wheel 0.9.1 or newer causes
install_name_tool
to error out on some libraries with the following error:There are a bunch of libraries in the wheel. Most of them get processed without incident. There's just something special about
libboost_atomic
that runs into this size limit.If this were happening in the code I build myself, I could just add the magic linker flag myself. However, Boost is installed via Anaconda and I don't control their build configuration.
I'm building against a Conda environment containing CPython 3.7.10 and Boost 1.75, both installed from
conda-forge
.To reproduce:
delocate-wheel test-wheel.whl
with delocate 0.9.1 or newer.I have a wheel file I can supply for debugging. It's 31MB and Github won't let me attach it to this message. Contact me and I'll arrange to get it to you.
Platform:
The text was updated successfully, but these errors were encountered: