On October 2, 2022 6:13 PM, Paul Smith wrote: >On Sun, 2022-10-02 at 17:48 -0400, rsbec...@nexbridge.com wrote: >> > I understand that this type of reuse makes things easier for the >> > gnulib folks, but for GNU make I'm not ready to drop support for >> > platforms that are not POSIX enough to run configure, and that don't >> > already have "make" available. So gnulib modules that require them >> > aren't available to GNU make (at least, not without modifications). >> >> Thank you for this comment. Gnulib is not available on the platform I >> maintain because of its high number of dependencies (including gcc >> itself, which cannot build on HPE NonStop). Keeping dependencies down >> is helpful for those outside of the explicit gcc support base. > >Really? I'd be pretty surprised if gnulib modules require GCC. In my >experience >gnulib-enabled software can be used with lots of compilers include MSVC and >Clang, plus others that are less well-known of course. >One of the main points of gnulib is to hide compiler differences (the other >being to >hide OS system differences). > >Gnulib does require a C compiler which is at least notionally C99 conforming, >though.
I was thinking of glibc, not gnulib. My bad. Still, recent version of gnulib have been problematic because of configure.
