So to this question, glibc 2.24 is the first release to loudly deprecate readdir_r. https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html
However, the docs summary mentioned below calls out reasons why readdir_r was never a good thing. So... What is our preferred solution as of 1.7.0? 1. Drop readdir[64]_r for readdir[64] always. 2. Allow readdir[64]_r with an autoconf toggle, skip detection. 3. Override readdir[64]_r detection with a test of ldd --version >= 2.24 I am leaning towards option 1 at this point, even as I was about to implement 3. On Sun, Mar 24, 2019, 18:13 William A Rowe Jr <wr...@rowe-clan.net> wrote: > AFAICT the very last 'nit' is our bad habit of using the deprecated > readdir_r()/readdir64_t() functions in modern gcc. Comparing ./configure > and make reminds me I had a kludge to finish in my working 1.7 tree. See > https://www.gnu.org/software/libc/manual/html_node/Reading_002fClosing-Directory.html > for a lengthy explanation. >
