On 2022-03-09 at 20:35 +0100, Andreas Schwab wrote: > On Mär 09 2022, Chet Ramey wrote: > > > Ultimately, this comes down to gaps in the release engineering. > > That won't help, the container image often comes from a different source > than the docker package.
The system (under all those conditions) was simply broken. access(2) didn't work. A good POSIX testsuite should have been able to catch it. I'm not sure there is one available out there. I don't know it, but there should be one. Then one could ask the reporter to run such standard testsuite... assuming one could guess that the problem might lie at that level. Ultimately, the problem is not new, configure scripts have been working around broken system functions for decades. containerizaion and other "new" layers are just providing more combinations where any of them could be faulty. Thanks for sharing the solution, Chet. These mysterious errors bring so much debugging "fun"... Cheers
