Re: build failure: malloc_np.h missing

[Thomas Klausner <wiz%gatalith.at@localhost>]

On Thu, Sep 26, 2024 at 02:24:21PM -0000, Christos Zoulas wrote:
> In article <ZvVksHjToQU_tpdU%exadelic.gatalith.at@localhost>,
> Thomas Klausner  <wiz%NetBSD.org@localhost> wrote:
> >On Thu, Sep 26, 2024 at 10:29:03AM +0200, Thomas Klausner wrote:
> >> Hi!
> >> 
> >> With latest source, I see
> >> 
> >> --- Process.lo ---
> >> In file included from
> >/usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Support/Process.cpp:108:
> >>
> >/usr/src/tools/llvm-lib/libLLVMSupport/../../llvm/../../external/apache2/llvm/lib/../dist/llvm/lib/Support/Unix/Process.inc:38:10: fatal error:
> >malloc_np.h: No such file or directory
> >>    38 | #include <malloc_np.h>
> >>       |          ^~~~~~~~~~~~~
> >> compilation terminated.
> >> 
> >> when building with
> >> 
> >> build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -T
> >/usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D
> >/usr/obj/amd64.gcc.20240926 -R /usr/obj/amd64.gcc.20240926.release
> >distribution
> >> 
> >> It's repeatable, on two consecutive tries.
> >
> >The problem is that this file expects malloc_np.h to exist when
> >HAVE_MALLCTL is set.
> 
> Should be fixed now. It was broken because mallctl was accidentally exposed.

Thanks.  The fix still means that ~two days of NetBSD-current/amd64
can not be used to build a new NetBSD-current: If one has the broken
version, then one needs to downgrade to a version before the switch to
the new jemalloc.
 Thomas