Closed compomega closed 5 years ago
despite the dates in this repository our libsysbase layer predates the posix dir by a few years. It serves much the same purpose but has a different approach in that we wanted to be able to have stuff configure without dependencies on the target libraries that provide the low level functionality. Trying to use the posix dir is "crossing the streams" so to speak.
We can look at providing fnmatch with libsysbase if it makes sense, we already provide scandir there. https://github.com/devkitPro/newlib/tree/devkitA64/libgloss/libsysbase.
Either way is fine with me.
Either way is fine with me.
Not an either way thing ... enabling that posix dir will break the toolchain ...
I mean I don't care which way it's fixed.
I have at least two libraries I'm trying to build that are trying to use fnmatch. One is configure based and the other is CMake based. The CMake based one is assuming the feature is there and not checking it (which sucks). For both it finds fnmatch.h but gets a linker error later. I can build it into my library (which is a bad idea) or hack the configure script output to not define HAVE_FNMATCH_H like so:
That is not ideal though. Is there a downside to building the posix implementation into libc? I see that opendir is still in libsysbase (hence the HAVE_OPENDIR define) after I make this change and half the posix files can be disabled or don't build anyway.