-
Notifications
You must be signed in to change notification settings - Fork 79
Add disable_initial_exec_tls feature for jemalloc-ctl #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
Conversation
jemalloc-ctl/Cargo.toml
Outdated
@@ -26,7 +26,7 @@ is-it-maintained-open-issues = { repository = "tikv/jemallocator" } | |||
maintenance = { status = "actively-developed" } | |||
|
|||
[dependencies] | |||
tikv-jemalloc-sys = { path = "../jemalloc-sys", version = "0.5.0" } | |||
tikv-jemalloc-sys = { path = "../jemalloc-sys", version = "0.5.0", default-features = false } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why need to disable default features?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just followed Cargo.toml from jemallocator folder, maybe I should not disable it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better keep it the old way, otherwise it becomes a broken change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: Likai Feng <[email protected]>
Aarch64 test has no machine from pingcap. |
@BusyJay Can you make a new release to crate.io? |
Published |
Default feature of tikv-jemalloc-sys can cause error when using pyo3 with jemalloc. Add disable_initial_exec_tls feature for jemalloc-ctl to avoid tikv-jemalloc-sys's default feature.
PyO3/pyo3#678