On 7/4/24 14:08, anlex N wrote:
I follow Paul Eggert's steps:
me@DESKTOP UCRT64 /e/workspace/github.com/gnu/gnulib
$ sh -x ./gnulib-tool --create-testdir --dir=/tmp/testdirr --verbose terminfo
Oh, I meant for you to run
sh -x ./gnulib-tool --list
as I thought you said that even a simple --list didn't work. However, it
seems that in this run you got further than before so perhaps you fixed
something.
/e/workspace/github.com/gnu/gnulib/gnulib-tool.py: *** could not patch
test-driver script
/e/workspace/github.com/gnu/gnulib/gnulib-tool.py: *** Stop.
Unfortunately the Python version of gnulib-tool doesn't have a readymade
debugging option like 'sh -x' to see what went wrong.
But do you have the 'patch' program installed? If not, that might
explain the problem. Please check all the programs listed in
DEPENDENCIES and make sure they're all installed.
As an aside to Collin, I see that patching is done via subprocess.call.
Since we're assuming Python 3.7 or later, shouldn't gnulib-tool.py be
using subprocess.run instead? That's what the Python documentation
recommends, and that way we could capture stderr and report it to the
user, which would help debug problems like this.
