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.
If anyone knows of anything else to address before we attempt to T&R a 1.7.0 release, please holler in the next day (this plea has been a standing request for nearly a month on the apr dev list.) Pre-tag retests on obscure architectures, which may have been disrupted by recent BSD/OSX fixes would be very much appreciated. On Wed, Feb 27, 2019, 17:06 William A Rowe Jr <wr...@rowe-clan.net> wrote: > With several new features added to the 1.7 branch, the fixes to the > Netware locking we had deferred, and the proposed correction of > SIGUSR2, I'm wondering what we see as remaining obstacles. > > I'd like to proceed with addressing the symlink vs. "other" reparse tag > questions raised for Windows, and will make the time to get the current > patch proposal and my type safety cleanups into trunk. PR 47630. > > I'm also interested in fixing SFU issues of the Ubuntu on Windows > implementation with APR locking, and can dedicate a few hours > this weekend to look at where those errors stand. > > Do we want to do something about de-prioritizing sysv semaphores > on linux by default with the 1.7.0 release? > > Any other concerns ahead of 1.7.0? > > Cheers, > > Bill > > >
