https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91833
--- Comment #3 from Pekka S <p...@gcc-bugzilla.mail.kapsi.fi> --- Well, actually I'm also using newlib (always using the latest trunk). It's configured and built as usual (not patching anything), but I don't think I've ever seen inhibit_libc being defined -- I did notice it in the lse-init.c, but I thought (as it wasn't being set for my configuration) it perhaps gates some other features. I'm not targetting any particular OS but using a bare bones setup. I've been using my build scripts for quite some time now (a couple of years?) and it's been all good so far; I use a couple of different newlib configurations (nano and non-nano). Perhaps I need to study what inhibit_libc affects, should it cause some other unwanted behaviour for my purposes, and where it would be detected in the configure scripts. Or, simply supply a stub sys/auxv.h and carry on.
