-
Notifications
You must be signed in to change notification settings - Fork 156
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
new version on mipsel 32 bit Atomic error #731
Comments
I believe this will be resolved by PyO3/pyo3#3619, which should be in a pyo3 release soon, and then we can include it. |
thx for the good info |
i add for me a temp fix oe-alliance/oe-alliance-core@7857a40 |
Ok! We'll put out a release for this shortly after pyo3 does.
…On Thu, Jan 18, 2024 at 3:12 PM Captain ***@***.***> wrote:
i add for me a temp fix ***@***.***
<oe-alliance/oe-alliance-core@7857a40>
—
Reply to this email directly, view it on GitHub
<#731 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBFOAW5AEL2C3U6SIOLYPF6ZTAVCNFSM6AAAAABB7XM23GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJZGEZTONJWHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
i need any info how can fix it
old version 4.01 works
all newer i get this
| error[E0432]: unresolved import
std::sync::atomic::AtomicI64
| --> /usr/src/debug/python3-bcrypt/4.1.2/cargo_home/bitbake/pyo3-0.20.0/src/impl_/pymodule.rs:6:25
| |
| 6 | use std::sync::atomic::{AtomicI64, Ordering};
| | ^^^^^^^^^
| | |
| | no
AtomicI64
insync::atomic
| | help: a similar name exists in the module:
AtomicI32
|
| For more information about this error, try
rustc --explain E0432
.The text was updated successfully, but these errors were encountered: