The os/posix/osdExecinfoBackTrace.cpp file is pretty simple, so someone could put a copy of it in the os/Linux directory which would then take precedence over the posix one for Linux targets. That would be where the code could explicitly look for glibc and uclib and assume musl if not – Michael's SourceForge page above provides help with how to detect the others. I don't know how many other libc's are in use on Linux, hopefully none of the others take musl's approach to compile-time identification.
The alternative would be to require musl users to add a line like
OP_SYS_CPPFLAGS += -D__MUSL__
to their configure/os/CONFIG_SITE.Common.linux-x86_64 file before building and to use that as another input to the macros in os/posix/osdExecinfoBackTrace.cpp.
We would be happy to see a patch file implementing one of these two approaches.
The os/posix/ osdExecinfoBack Trace.cpp file is pretty simple, so someone could put a copy of it in the os/Linux directory which would then take precedence over the posix one for Linux targets. That would be where the code could explicitly look for glibc and uclib and assume musl if not – Michael's SourceForge page above provides help with how to detect the others. I don't know how many other libc's are in use on Linux, hopefully none of the others take musl's approach to compile-time identification.
The alternative would be to require musl users to add a line like os/CONFIG_ SITE.Common. linux-x86_ 64 file before building and to use that as another input to the macros in os/posix/ osdExecinfoBack Trace.cpp.
OP_SYS_CPPFLAGS += -D__MUSL__
to their configure/
We would be happy to see a patch file implementing one of these two approaches.