0% tests passed, 3 tests failed out of 3

[dougmencken]

$ make test
Running tests...
/usr/bin/ctest --force-new-ctest-process
Test project /Volumes/hfsplushd/Development/gcc-toolchain/xtools-git-dougmencken/_build
    Start 1: check-x86-as
1/3 Test #1: check-x86-as .....................***Failed    0.11 sec
    Start 2: check-x86_86-as
2/3 Test #2: check-x86_86-as ..................***Failed    0.09 sec
    Start 3: check-ppc-as
3/3 Test #3: check-ppc-as .....................***Failed    0.07 sec

0% tests passed, 3 tests failed out of 3

Total Test time (real) =   0.32 sec

The following tests FAILED:
	  1 - check-x86-as (Failed)
	  2 - check-x86_86-as (Failed)
	  3 - check-ppc-as (Failed)
Errors while running CTest
make: *** [test] Error 8

[dougmencken]

That’s how I configure it

cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=/opt/xtools \
      -DCMAKE_C_COMPILER:STRING=/Developer/GCC/8.2p/PowerPC/32bit/bin/gcc \
      -DCMAKE_CXX_COMPILER:STRING=/Developer/GCC/8.2p/PowerPC/32bit/bin/g++ \
      -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=$(printf 10.%d `sw_vers -productVersion | cut -d . -f 2`) \
      -DCMAKE_C_FLAGS:STRING=-mmacosx-version-min=$(printf 10.%d `sw_vers -productVersion | cut -d . -f 2`) \
      -DCMAKE_CXX_FLAGS:STRING=-mmacosx-version-min=$(printf 10.%d `sw_vers -productVersion | cut -d . -f 2`) \
      ..

[iains]

Thanks for the report.

as noted in the build instructions:

"at present there's not a usable test-suite (although using the resulting tools to build GCC/LLVM is a fairly good test)." Actually, "fairly" is somewhat of an understatement - building a toolchain is an extensive use of the tool capabilities. The compiler test suite, in turn, exercises the assembler and linker.

So - the failures you see in attempting the ctest invocation are not, in themselves, significant

• fixing up the test suite for 1.1 is probably not going to happen (since I have a pending update to 2.2.2, where it would be more productive to invest the time).