Jay
I would like to also hear from @sunxiaoguang @zhangjinpeng1987 > To make sure there's no significant bug , I will add more unit test for this project in the future...
jemalloc relies on configure to bootstrap the build system, I'm not sure how to do so without sh. I believe https://github.com/jemalloc/jemalloc/issues/303 is required to achieve cross platform support.
You can check https://github.com/jemalloc/jemalloc/blob/dev/INSTALL.md#building-for-windows for prerequisites of Windows platform.
Seems easy to fix, do you want to send a patch?
Issue in jemalloc: https://github.com/jemalloc/jemalloc/issues/2014
Can you upload the Makefile after configure? It should be stored in "{rust-jemalloc-dir}/target/debug/build/jemalloc-sys-{hash}/out/build/Makefile".
See #56. I'm afraid we have to keep using tikv-jemallocator.
That might work too. However, we have made the claim in the last release that tikv-jemallocator is preferred than jemallocator for new projects. Changing it back and forth may cause...
`CStr` should be used.
It seems to be an issue of jemalloc itself. You may want to send the issue to https://github.com/jemalloc/jemalloc.