Open me-and opened 10 years ago
Huh, that's interesting. If you skip the make configure && ./configure
stages of the build process and just run make
, the test continues to fail.
I thought it might be the --with-libpcre
argument to ./configure
which was causing the difference, but running ./configure
without it produces the same result...
Just checked for comparison on my CentOS VM: whether or not you include the configure
step, that test always fails.
Next step is probably to report this upstream.
Now this is odd: building using Cygport has the test unexpectedly passing, but building directly from a Git source tree including the Cygwin patches has the test failing!
Ah, here we go: the Cygport compilation runs make configure
and ./configure --htmldir=<dir> --mandir=<dir> --with-libpcre
before make
. Presumably at least part of that is what's making the difference here.
… which is something I'd already discovered in my notes above. OH WELL.
Reported this upstream: http://lists-archives.com/git/864215-binary-grep-t7008-known-breakage-vanished-on-cygwin.html.
Test is now t7815, still passing at 811da4d0e9d82be6f99834e0799d8a41a5cbbe9f (v2.26.1) when marked as an expected failure.
The
t7008-grep-binary.sh
test "git grep .fi a
" passes. It's marked as an expected failure, and it does fail on my v2.0.4 Git build on CentOS.