jemallocator
jemallocator copied to clipboard
Rust allocator using jemalloc as a backend
``` error: failed to run custom build command for `tikv-jemalloc-sys v0.5.4+5.3.0-patched` Caused by: process didn't exit successfully: `/Users/djc/src/rustls/target/debug/build/tikv-jemalloc-sys-535ae77c5e13eddf/build-script-build` (exit status: 101) --- stdout TARGET=aarch64-apple-darwin HOST=aarch64-apple-darwin NUM_JOBS=10 OUT_DIR="/Users/djc/src/rustls/target/debug/build/tikv-jemalloc-sys-6b3cd5a322213ff7/out" BUILD_DIR="/Users/djc/src/rustls/target/debug/build/tikv-jemalloc-sys-6b3cd5a322213ff7/out/build" SRC_DIR="/Users/djc/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tikv-jemalloc-sys-0.5.4+5.3.0-patched" cargo:rustc-cfg=prefixed...
jemalloc defaults to enabling stats if `--enable-stats` is not present and `--disable-stats` was not set: https://github.com/jemalloc/jemalloc/blob/fa451de17fff73cc03c31ec8cd817d62927d1ff9/configure.ac#L1331-L1333 This issue was observed when we were building with `stats` and noticed the output...
As seen with: ``` git clone https://github.com/tikv/jemalloc Cloning into 'jemalloc'... ... [dell ~/t]% cd jemalloc [dell ~/t/jemalloc]% git log -1 5.3.0 fatal: ambiguous argument '5.3.0': unknown revision or path not...
I have come across a closed issue(#33 ) that described the phenomenon. Upon verification, it seems that it is necessary to enable the debug=true option in the cargo build command....
Hi, I thought that frawk was not supported on Windows, but I came about this [#87](https://github.com/ezrosent/frawk/issues/87) issue where I saw that using `cargo build --no-default-features` does (or might) compile. I...
While analyzing the issue mentioned in https://github.com/ezrosent/frawk/issues/87, I found that `tikv-jemalloc-sys` (`build.rs`) relays on `sh` during its build process. As jemalloc, [more or less](https://github.com/jemalloc/jemalloc/issues/1703), supports native compilation on Windows without...
to reproduce: ```bash cd /tmp mkdir "j (1)" cd "j (1)" git clone --recursive https://github.com/tikv/jemallocator cd jemallocator/jemalloc-sys cargo build ``` result: ``` Compiling libc v0.2.138 Compiling fs_extra v1.2.0 Compiling cc...
``` = note: /usr/bin/ld: /home/work/databend/target/x86_64-unknown-linux-musl/debug/deps/libtikv_jemalloc_sys-5844e04c26a2be2a.rlib(prof_sys.pic.o): undefined reference to symbol 'pthread_getname_np@@GLIBC_2.34' /usr/bin/ld: /usr/lib64/libc.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status ``` target: x86_64-unknown-linux-musl...
Since tikv/jemallocator has become the upstream of `jemallocator`, I believe it's time to replace all `tikv-jemallocator` to `jemallocator` to avoid confusion. And we should push a new version to `tikv-jemallocator`...