sergiodj opened a new issue, #3482:
URL: https://github.com/apache/kvrocks/issues/3482

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
   
   
   ### Version
   
   I'm using GCC 16 on GNU/Linux (Wolfi OS).
   
   ### Minimal reproduce step
   
   Build the package with GCC 16.  Here are the cmake flags I'm using:
   
   ```
           -DENABLE_OPENSSL=ON \
           -DPORTABLE=1 \
           -DCMAKE_BUILD_TYPE=Release \
   ```
   
   ### What did you expect to see?
   
   The build succeeds.
   
   ### What did you see instead?
   
   The following error (due to `jemalloc`, which is a build dependency):
   
   ```
   2026/05/06 14:27:16 INFO 
/home/build/output/_deps/jemalloc-src/src/jemalloc_cpp.cpp: In function 'void* 
handleOOM(std::size_t, bool)':
   2026/05/06 14:27:16 INFO 
/home/build/output/_deps/jemalloc-src/src/jemalloc_cpp.cpp:103:22: error: 
'__throw_bad_alloc' is not a member of 'std'; did you mean '__throw_bad_cast'?
   2026/05/06 14:27:16 INFO   103 |                 std::__throw_bad_alloc();
   2026/05/06 14:27:16 INFO       |                      ^~~~~~~~~~~~~~~~~
   2026/05/06 14:27:16 INFO       |                      __throw_bad_cast
   2026/05/06 14:27:16 INFO make: *** [Makefile:533: src/jemalloc_cpp.o] Error 1
   2026/05/06 14:27:16 INFO make: *** Waiting for unfinished jobs....
   2026/05/06 14:27:16 INFO
   ```
   
   ### Anything Else?
   
   jemalloc fixed the issue upstream: 
https://github.com/jemalloc/jemalloc/commit/1a15fe33a48c52bfe26ea83e49f0d317a47da3ea
   
   I understand that the fix hasn't been released yet, but I decided to report 
the bug to Apache Kvrocks so that you're aware that jemalloc will need to be 
updated soon.
   
   Thanks!
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to