On 2013-04-16, at 5:16 PM, Ralph Moritz ralph.moeritz@outlook.com wrote:
On Tue, 16 Apr 2013 23:02:01 +0200, Marc Feeley feeley@iro.umontreal.ca wrote:
Thank you very much, `make' now completes without error. I'm not sure if it's anything to worry about, but `make check' wrote the following to stderr at the end of its run:
make[1]: *** [test1] Error 1 make: *** [check] Error 2
Is this something to be concerned about?
Perhaps. Can you send me the output of the "make check". It runs fine on my MinGW installation.
When I run `make check' the file `tests/test1.out' is created. This file is identical to `tests/test1.ok' according to diff, so I'm not sure there's any value in sending it.
Are the files the same length? Maybe it is a difference in the end-of-line encoding (lf vs. cr-lf).
Yep, differences are in end-of-line encoding, probably due to my git settings. Didn't catch it because I ran diff as `diff -qw test1.ok test1.out'.
I see. So the file with the cr-lf end-of-line encoding is the test1.ok file, not the test1.out file (which has lf end-of-line encoding reliably on all OSes). I wonder how I could force git to treat test1.ok as a binary file. In fact I don't see how git can be so confident that test1.ok is a text file to change the lf to cr-lf.
Marc