conflict (Was Re: gv)

Igor Pechtchanski
Sun Jun 20 02:54:00 GMT 2004

On Sat, 19 Jun 2004, Thomas Dickey wrote:

> On Fri, Jun 18, 2004 at 10:45:07PM -0400, Igor Pechtchanski wrote:
> > One more thing: "make check" doesn't work when built outside of the source
> > directory (the build itself is fine).  I think changing "./" to
> > "${srcdir}/" should fix it, but I'm not sure, so I'll leave it
> > up to you.  Also, when testing, a file called "conflict" is blindly
> > removed and created in /tmp, and the test itself doesn't seem to work
> > under Cygwin (i.e., reports no conflicts).  Could the latter have
> > something to do with the .exe extension (just a guess)?  I'll check later.
> I think Cygwin's chmod simply didn't believe the file was a script.
> So I tweaked its contents to help, will test that tomorrow...

Actually, looks like the file created is "conflict", and the tested
conflict executable is "conflict.exe".  It doesn't look like .exe is part
of FileTypes by default, so no conflict is found.  Another clue is that
"conflict -t.exe." works...  FWIW, "." is explicitly added to the PATH in

BTW, while we're discussing, would it be possible to first
create a unique directory, and then create the test executable in that
directory, instead of doing it straight in /tmp?  Something like

DIR=`mktemp -d /tmp/conflict.$$.XXXXXXXX`
cd $DIR
touch conflict
chmod 755 conflict
rm -f conflict
cd /tmp
rm -rf $DIR

I can submit the above as a patch if it helps.
      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

More information about the Cygwin-xfree mailing list