bug#22856: "make check" can start a shell on binary data

2016-02-29 Thread Nick Bowler
On 2016-02-29, Vincent Lefevre wrote: > When I cross-compile for Windows and run "make check" without > LOG_COMPILER=wine (by mistake), strange files appear. [...] > ./tadd.exe: 1: ./tadd.exe: MZ ��¸@€º´: not found > ./tadd.exe: 2: ./tadd.exe: : not found > ./tadd.exe: 1: ./tadd.exe: @.bss €: not

bug#22856: "make check" can start a shell on binary data

2016-02-29 Thread Vincent Lefevre
Sorry, forget this bug report. After wondering where the problem came from exactly, I've eventually found that this is some incredible bug in dash! -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - comput

bug#22856: "make check" can start a shell on binary data

2016-02-29 Thread Vincent Lefevre
When I cross-compile for Windows and run "make check" without LOG_COMPILER=wine (by mistake), strange files appear. For instance, as a simple example with MPFR: cventin:...re/mpfr-3.1/tests> make tadd.log FAIL: tadd.exe The failure is expected, but I get: -rw-r--r-- 1491 2016-02-29 19:39:24