First of all, I built binutils-2.19.1 _without_ i686-pc-mingw32, i.e. not having cross-compilation in mind, and I had no problems whatsoever during the build process. Then I changed just one factor - added "--target=i686-pc-mingw32" (I am building from scratch), and 'make check' failed with these failures: ERROR: /mnt/sdb8/sergei/AFSWD_debug/build/binutils-2.19.1/ld/testsuite/ld-elf/eh-group1.s: assembly failed FAIL: Link eh-group.o to eh-group Running /mnt/sdb8/sergei/AFSWD_debug/build/binutils-2.19.1/ld/testsuite/ld-scripts/weak.exp ... FAIL: weak symbols . I am about to upload files with details (command lines, etc.)
Created attachment 3871 [details] autogenerated script used to run 'configure'
Created attachment 3872 [details] configure screen output
Created attachment 3873 [details] 'make check' screen output
If it matters, my system is: uname -a Linux amdam2 2.6.22.19-0.2-default #1 SMP 2008-12-18 10:17:03 +0100 i686 athlon i386 GNU/Linux - SUSE 10.3, but I am using self-built gcc-4.3.3 to build binutils-2.19.1.
Hi Sergei, Both of these problems boils down to the fact that the mingw32 target uses a different binary file format (PE) when compared to your native file format (ELF). The eh-group tests only work on ELF targets so they should not have been run for the i686-pc-mingw32. (This has been fixed in the mainline sources). Support for weak symbols in PE format files is under active development at the moment, so the tests have been left active, even though they are known to fail for PE targets. Cheers Nick