In <http://lists.gnu.org/archive/html/bug-coreutils/2007-02/msg00290.html> Elias Pipping <[EMAIL PROTECTED]> writes:
> The actual problem (while these binaries work flawlessly for me) > is that 'make check' fails (see cmd_output_tail) Most likely the problem is that 'configure' is probing your build architecture, and is coming up answers appropriate for that architecture, but then you are running on a different architecture. Given that md5sum fails, the first suspect would be WORDS_BIGENDIAN in lib/config.h. That is, I suspect that WORDS_BIGENDIAN should have different values on your different architectures. To help debug this, can you please try modifying your lib/config.h by replacing these lines: /* Define to 1 if your processor stores words with the most significant byte first (like Motorola and SPARC, unlike Intel and VAX). */ /* #undef WORDS_BIGENDIAN */ with these lines: /* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most significant byte first (like Motorola and SPARC, unlike Intel and VAX). */ #if defined __BIG_ENDIAN__ # define WORDS_BIGENDIAN 1 #elif ! defined __LITTLE_ENDIAN__ /* #undef WORDS_BIGENDIAN */ #endif and then do a "make clean; make"? Then you can do a "make check" on both architectures. I will CC: this to bug-gnulib and bug-autoconf to give people a heads-up on this issue. In general the build != execute problem is a severe one with lots of issues, but for the particular combination of Power Mac and Intel this may be the only issue for coreutils.
