Hi Andreas, Thanks for the bug report.
On Fri, Sep 29, 2017 at 10:55:59PM +0200, Andreas Beckmann wrote: > jemalloc 5 FTBFS on all 32-bit architectures since the signatures for > operator new/delete have changed with GCC 7: I don't think it's a GCC 7 issue. I think it was just a packaging error on my side, where I used "unsigned long" as the argument, unconditionally, while it's (obviously, in hindsight) "unsigned int" on 32-bit architectures. (Note that jemalloc 5.0.1-1 is the first one with C++ ABI, so this is all new) I've fixed this in git a while ago[1] but haven't uploaded because that version has a bunch of FTBFSes in other architectures, that I've been engaging with upstream about[2][3]. It's taking longer than I originally expected, but still, it's in experimental, so I didn't think there was much point in making a new upload that builds in a few more architectures but still fails on many. Regards, Faidon 1: https://anonscm.debian.org/cgit/collab-maint/jemalloc.git/commit/?h=experimental&id=4dc71357fd2a3f77ab63476d0da4f0d5581463d9 2: https://github.com/jemalloc/jemalloc/issues/979 3: https://github.com/jemalloc/jemalloc/issues/999
