Re: Latest Coreutils

[Jim Meyering]

Elbert_Gmail <address@hidden> wrote:
> I attached the log file.

Thanks.
Next time, please omit the lines that merely show how gcc is invoked.

...
> mv -f .deps/test-xvasprintf.Tpo .deps/test-xvasprintf.Po
> gcc -std=gnu99  -D__EMX__ -DEMX -DOS2  -D__ST_MT_ERRNO__ -O3 -march=pentium 
> -mtune=pentium4  -Zexe -Zomf -Zmap -Zargs-wild -D__ST_MT_ERRNO__ -s -o 
> test-xvasprintf.exe test-xvasprintf.o libtests.a ../lib/libcoreutils.a 
> libtests.a
> gcc -std=gnu99  -I. -I../lib  -I. -I. -I.. -I./.. -I../lib -I./../lib   
> -D__EMX__ -DEMX -DOS2  -D__ST_MT_ERRNO__ -O3 -march=pentium -mtune=pentium4 
> -MT test-yesno.o -MD -MP -MF .deps/test-yesno.Tpo -c -o test-yesno.o 
> test-yesno.c
> mv -f .deps/test-yesno.Tpo .deps/test-yesno.Po
> gcc -std=gnu99  -D__EMX__ -DEMX -DOS2  -D__ST_MT_ERRNO__ -O3 -march=pentium 
> -mtune=pentium4  -Zexe -Zomf -Zmap -Zargs-wild -D__ST_MT_ERRNO__ -s -o 
> test-yesno.exe test-yesno.o libtests.a ../lib/libcoreutils.a libtests.a
...
> FAIL: test-canonicalize.sh.log
...
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-frexp-nolibm.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-frexpl-nolibm.exe.log
...
> FAIL: test-gethostname.exe.log
...
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-isnand-nolibm.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-isnanf-nolibm.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-isnanl-nolibm.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-math.exe.log
...
> [1]   Abort trap              EXEEXT=".exe" US...
> FAIL: test-open.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-printf-frexp.exe.log
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-printf-frexpl.exe.log
...
> [1]   Floating point exception EXEEXT=".exe" US...
> FAIL: test-signbit.exe.log
...
> [1]   Abort trap              EXEEXT=".exe" US...
> FAIL: test-stat-time.exe.log
...

If you're inclined to investigate, the above failures should be
diagnosed and probably solved before anything else.
[plus a few other *printf failures]