We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
pytorch has reported an issue on aarch64 where they use auditwheel to repair wheels. After 6.3.0, they've reported pytorch/pytorch#149471.
auditwheel
While we're also using auditwheel to repair torch wheels, this do not break our release.
I might be able to look into this later.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
I've ran into this, but cannot reproduce stably
The reason is when we have two dependencies: a.so -> b.so -> c.so and a.so -> c.so.
The order to precess dependencies of a.so is random (for from a set):
for
auditwheel/src/auditwheel/lddtree.py
Line 518 in ff5b637
When b.so do not have correct rpath for c.so, and if we process b.so first, _all_libs["c.so"] would not have the path and not updated later.
_all_libs["c.so"]
Successfully merging a pull request may close this issue.
Uh oh!
There was an error while loading. Please reload this page.
pytorch has reported an issue on aarch64 where they use
auditwheel
to repair wheels. After 6.3.0, they've reported pytorch/pytorch#149471.While we're also using auditwheel to repair torch wheels, this do not break our release.
I might be able to look into this later.
The text was updated successfully, but these errors were encountered: