On Thu, Dec 27, 2012 at 04:06:47PM +0100, Andreas Schwab wrote:
> Jack Howarth <howa...@bromo.med.uc.edu> writes:
>
> > Did you run make check in libffi on this merge? These changes
> > appear to have broken the dejagnu testing in libffi...
>
> The problem is the wrong definition of load_gcc_lib.
>
> @@ -16,7 +16,7 @@
>
> proc load_gcc_lib { filename } {
> global srcdir
> - load_file $srcdir/../../gcc/testsuite/lib/$filename
> + load_file $srcdir/lib/$filename
> }
>
> load_lib dg.exp
>
> Andreas.
Andreas,
What do you get for the testsuite results with that change? On
x86_64-apple-darwin12, every single test seems to fail the
test for excess errors at -m32 (but not -m64) when using...
make -k check RUNTESTFLAGS="--target_board=unix'{-m32,-m64}'"
=== libffi Summary for unix/-m32 ===
# of unexpected failures 663
# of unresolved testcases 663
# of unsupported tests 55
These show up at -m32 as...
Executing on host: /sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/gcc/xgcc
-B/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/gcc/
../../../../gcc-4.8-20121226/libffi/testsuite/libffi.call/closure_fn0.c -O0 -W
-Wall
-I/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/x86_64-apple-darwin12.2.0/libffi/testsuite/../include
-I../../../../gcc-4.8-20121226/libffi/testsuite/../include
-I/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/x86_64-apple-darwin12.2.0/libffi/testsuite/../include/..
-L/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/x86_64-apple-darwin12.2.0/libffi/testsuite/../.libs
-Wl,-allow_stack_execute -shared-libgcc -lffi -lm -m32 -o ./closure_fn0.exe
(timeout = 300)
ld: warning: ignoring file
/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/x86_64-apple-darwin12.2.0/libffi/.libs/libffi.dylib,
file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x
0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture
being linked (i386):
/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/x86_64-apple-darwin12.2.0/libffi/.libs/libffi.dylib^M
Undefined symbols for architecture i386:^M
"_ffi_closure_alloc", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_prep_cif", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_prep_closure_loc", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_type_double", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_type_float", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_type_sint16", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_type_sint32", referenced from:^M
_main in ccIwL8dt.o^M
"_ffi_type_uint64", referenced from:^M
_main in ccIwL8dt.o^M
ld: symbol(s) not found for architecture i386^M
collect2: error: ld returned 1 exit status^M
So it appears that the merge also broke the multilib testing of libffi.
Jack
>
> --
> Andreas Schwab, sch...@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
