hi!

> ## --------- ##
> ## Platform. ##
> ## --------- ##
> 
> hostname = Cosimo-Capronis-iPad
> uname -m = iPad2,1
> uname -r = 11.0.0
> uname -s = Darwin
> uname -v = Darwin Kernel Version 11.0.0: Sun Apr  8 21:51:47 PDT 2012; 
> root:xnu-1878.11.10~1/RELEASE_ARM_S5L8940X

Wow, that's an unusual platform!

There are weird messages from your compiler in there.
For instance:

> ./headers.at:258: $CXX $CXXFLAGS $CPPFLAGS $LDFLAGS c-only.o cxx-only.o -o 
> c-and-cxx ||
>           exit 77
> --- /dev/null 2013-09-01 10:49:17.000000000 +0200
> +++ /var/root/bison-3.0/tests/testsuite.dir/at-groups/184/stderr      
> 2013-09-01 10:49:50.000000000 +0200
> @@ -0,0 +1 @@
> +codesign_allocate -i c-and-cxx -a armv6 224 -o .c-and-cxx.cs
> stdout:
> 184. headers.at:112: 184. Several parsers (headers.at:112): FAILED 
> (headers.at:258)

Apparently, it dumps information on stderr when linking.  Can
you mute that?


Elsewhere:

> ./regression.at:1154: $CC $CFLAGS $CPPFLAGS $LDFLAGS -o input input.c $LIBS
> stderr:
> clang: error: invalid arch name '-arch thumbv6'
> Assertion failed: (TargetInitialized && "Target not initialized!"), function 
> isTargetIPhoneOS, file 
> /private/var/distfiles/llvm/llvm-3.3.src/tools/clang/lib/Driver/ToolChains.h, 
> line 226.
> 0  clang             0x01b882b4 llvm::sys::PrintStackTrace(__sFILE*) + 44
> 1  clang             0x01b885c0 _ZL28PrintStackTraceSignalHandlerPv + 24
> 2  clang             0x01b88894 _ZL13SignalHandleri + 688
> 3  libsystem_c.dylib 0x33d1b7e3 _sigtramp + 38
> 4  libsystem_c.dylib 0x33d1120f pthread_kill + 54
> 5  clang             0x000635b4 abort + 20
> 6  clang             0x00063594 __assert_rtn + 100
> 7  clang             0x001367f8 
> clang::driver::toolchains::Darwin::TranslateArgs(clang::driver::DerivedArgList
>  const&, char const*) const + 7412
> 8  clang             0x0011964c 
> clang::driver::Compilation::getArgsForToolChain(clang::driver::ToolChain 
> const*, char const*) + 148
> 9  clang             0x001262f4 
> clang::driver::Driver::BuildJobsForAction(clang::driver::Compilation&, 
> clang::driver::Action const*, clang::driver::ToolChain const*, char const*, 
> bool, bool, char const*, clang::driver::InputInfo&) const + 1400
> 10 clang             0x001223ac 
> clang::driver::Driver::BuildJobs(clang::driver::Compilation&) const + 608
> 11 clang             0x0011e058 
> clang::driver::Driver::BuildCompilation(llvm::ArrayRef<char const*>) + 1752
> 12 clang             0x0006da34 main + 10520
> 13 clang             0x00066ecc start + 52
> Stack dump:
> 0.    Program arguments: /usr/local/bin/clang -mios-version-min=4.2.1 -arch 
> thumbv6 -g -O2 -I/var/root/bison-3.0/lib -o input input.c 
> /var/root/bison-3.0/lib/libbison.a 
> 1.    Compilation construction
> 2.    Building compilation jobs
> 3.    Building compilation jobs
> /usr/bin/clang: line 18: 71241 Trace/BPT trap: 5       /usr/local/bin/clang 
> -mios-version-min=4.2.1 -arch thumbv6 $@
> stdout:
> ./regression.at:1155:  $PREPARSER ./input
> stderr:
> /var/root/bison-3.0/tests/testsuite.dir/at-groups/352/test-source: line 293: 
> ./input: No such file or directory
> ./regression.at:1155: exit code was 127, expected 0
> 352. regression.at:1116: 352. Token number in precedence declaration 
> (regression.at:1116): FAILED (regression.at:1155)

And also:

> 405. cxx-type.at:394: testing GLR: Resolve ambiguity, impure, no locations ...
> ./cxx-type.at:395: bison -fno-caret -o types.c types.y
> stderr:
> types.y:76.8-37: warning: unset value: $$ [-Wother]
> types.y: warning: 1 reduce/reduce conflict [-Wconflicts-rr]
> ./cxx-type.at:395: $BISON_C_WORKS
> stderr:
> stdout:
> ./cxx-type.at:395: $CC $CFLAGS $CPPFLAGS $LDFLAGS -o types types.c $LIBS
> stderr:
> ld: warning: unexpected relocation type 9
[230 more copies of these lines suppressed]
> ld: warning: unexpected srelocation type 9
> clang: error: unable to execute command: posix_spawn failed: No such file or 
> directory
> clang: error: dsymutil command failed with exit code 1 (use -v to see 
> invocation)
> codesign_allocate -i types -a armv7 320 -o .types.cs
> stdout:

So your tool chain does not seem to be strong enough to run the
test suite.  If you have suggestions on how to address these
issues, please, let us know.

Reply via email to