Hi, James Youngman wrote: > It appears that the test in gnulib/m4/getcwd-path-max.m4 fails on Mac OS X > 10.5.8, leaving behind a deep directory tree that $ac_clean_files doesn't > properly clean up.
This is not what I see. On the Mac OS X 10.5.8 system I have access to (x86_64), a testdir for module 'getcwd', created through ./gnulib-tool --create-testdir --dir=../testdir5 --single-configure getcwd configures and builds fine. There is no directory tree left over (both before and after Paul Eggert's 2024-04-01 patch). The configure findings regarding 'getcwd' are: checking whether getcwd (NULL, 0) allocates memory for result... yes checking for getcwd with POSIX signature... yes checking whether getcwd is declared... yes checking whether getcwd handles long file names properly... yes, but with shorter paths checking whether getcwd succeeds when 4k < cwd_length < 16k... no > Is there any way to get "configure" to succeed on such a platform? Well, I don't know what the problem on your machine actually is. > Is Mac OS X 10.5.8 still a supported target for gnulib? The currently supported macOS versions are 12, 13, 14. I happen to still have access to a Mac OS X 10.5.8, but that is not a reason for investing too much time into support this old version. > If additional details are needed, please see the original bug report at > https://savannah.gnu.org/bugs/index.php?57461 I don't want to revive the thread between Paul Eggert and Peter Dyballa at <https://lists.gnu.org/archive/html/bug-gnulib/2024-03/threads.html#00208>. In my opinion, it was a fruitless time sink. Bruno
