> Am 11.1.2022 um 18:29 schrieb Paul Eggert <[email protected]>:
>
> On 1/11/22 03:43, Peter Dyballa wrote:
>> This way you can draw your own conclusions.
>
> Thanks, but I think the problem has been diagnosed (see my previous email).
> Someone would need to implement the solution, though. I hope that's something
> you can do....
With Ryan's help this should be possible, because he is a MacPorts professional
and I am only a user.
For me one question is important: why is configure producing different results
in two different environments? In my private environment it seems to find the
proper depth while in MacPorts' environment it has to run the directory tree
test. In the latter it runs as root…
One proposal I made to MacPorts was to make configure accept the first failure
and then try again with a directory name that is one byte or character longer.
This worked kind of manually (by patching the configure script appropriately
before the MacPorts build process starts).
--
Greetings
Pete
When in doubt, use brute force.
– Ken Thompson
