Alpine (musl) does not provide mallinfo.
I'm trying to build the GN, but it seems they (Google?) try to do malloc interposition in a glibc specific way. I couldn't just get rid of mallinfo usage or dummy it out (eg. always print 0 byte is in use).
I got some advice from the musl developers:
mallinfo api does not work on 64bit systems and assumes a particular malloc implementation so it is not useful for anything serious.
Introspective backtracing and malloc interposition is not possible to do portably and thus should be optional.
People who write build systems should learn to write portable code.. otherwise their build system will cause more problems than it solves.
Now I'm looking for a way to disable those allocator hacks, and not getting a Segmentation fault.
Also I have open an issue in V8, but it looks like a patch in the near future is not expected.
Alpine (musl) does not provide
mallinfo
. I'm trying to build the GN, but it seems they (Google?) try to do malloc interposition in a glibc specific way. I couldn't just get rid ofmallinfo
usage or dummy it out (eg. always print 0 byte is in use).I got some advice from the musl developers:
Now I'm looking for a way to disable those allocator hacks, and not getting a Segmentation fault. Also I have open an issue in V8, but it looks like a patch in the near future is not expected.