> Am 11.01.2022 um 00:35 schrieb Paul Eggert <egg...@cs.ucla.edu>:
>
> On 1/9/22 03:10, Peter Dyballa wrote:
>> checking whether getcwd aborts when 4k < cwd_length < 16k... yes
>> and of course the reports about not being able to remove the
>> "confdir-14B---" and "confdir3" directory trees,
>
> So, the problem is that the test program creates the deep directories, and
> then runs a test that aborts the test program, and this means the test
> program can't clean up after itself?
>
> If so, perhaps we should alter the test program so that it can be run in such
> a way that it *only* cleans up after itself, and we use that for cleanup
> since macOS 'rm' isn't up to the task.
Hello Paul!
Since neither me nor any other Mac user or MacPorts maintainer is able to
implement your solution, would it be possible to put this test into a clause
that only comes true on systems that need this directory depth test? As far as
I understood this test is only needed on (some?) AIX versions…
Recently some more users of MacPorts complained, so I am kind of reopening this
bug report. This is a problem notable for being wide-spread, being present in
at least a few GNU utilities: m4 1.4.19, findutils 4.6.0 and 4.7.0, bison
3.8.2, coreutils 9.1, gzip-1.4.
--
Greetings
Pete
Journalism is printing what someone else does not want printed; everything else
is public relations.
– George Orwell
