On Thu, Feb 27, 2020 at 5:18 PM Maciej W. Rozycki <ma...@wdc.com> wrote: > > Fix a problem with the libffi testsuite using a method to determine the > compiler to use resulting in the tool being different from one the > library has been built with, and causing a catastrophic failure from the > inability to actually choose any compiler at all in a cross-compilation > configuration. > > Address this problem by providing a DejaGNU configuration file defining > the compiler to use, via the GCC_UNDER_TEST TCL variable, set from $CC > by autoconf, which will have all the required options set for the target > compiler to build executables in the environment configured, removing > failures like: > > FAIL: libffi.call/closure_fn0.c -W -Wall -Wno-psabi -O0 (test for excess > errors) > Excess errors: > default_target_compile: No compiler to compile with > UNRESOLVED: libffi.call/closure_fn0.c -W -Wall -Wno-psabi -O0 compilation > failed to produce executable > > and bringing overall test results for the `riscv64-linux-gnu' target > (here with the `x86_64-linux-gnu' host and RISC-V QEMU in the Linux user > emulation mode as the target board) from: > > === libffi Summary === > > # of unexpected failures 708 > # of unresolved testcases 708 > # of unsupported tests 30 > > to: > > === libffi Summary === > > # of expected passes 1934 > # of unsupported tests 28 > > Also respect the TOOL_EXECUTABLE TCL variable for a standalone run via > `runtest' and remove an unused TOOL_OPTIONS TCL variable instance. > > libffi/ > * configure.ac: Add testsuite/libffi-site-extra.exp to output > files. > * configure: Regenerate. > * testsuite/libffi-site-extra.exp.in: New file. > * testsuite/Makefile.am (EXTRA_DEJAGNU_SITE_CONFIG): New > variable. > * testsuite/Makefile.in: Regenerate. > * testsuite/lib/libffi.exp (libffi-init): Handle GCC_UNDER_TEST. > (libffi_target_compile): Likewise.
Upstream libffi has local.exp. Is that possible to use the same file? -- H.J.
