On 10/10/2009 11:53, [email protected] wrote: > JonY wrote: >> On 10/10/2009 09:45, [email protected] wrote: >>> [email protected] wrote: >>>> JonY wrote: >>>>> On 10/10/2009 08:04, [email protected] wrote: >>>>>> [email protected] wrote: >>>>>>> [email protected] wrote: >>>>>>>> x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -m32 -pipe -std=gnu99 >>>>>>>> -Wall -Wextra -Wformat -Wstrict-aliasing -Wshadow -Wpacked -Winline >>>>>>>> -Wimplicit-function-declaration -Wmissing-noreturn >>>>>>>> -Wmissing-prototypes -O3 -mms-bitfields -MT >>>>>>>> profile/lib32_libgmon_a-profil.o -MD -MP -MF >>>>>>>> profile/.deps/lib32_libgmon_a-profil.Tpo -c -o >>>>>>>> profile/lib32_libgmon_a-profil.o `test -f 'profile/profil.c' || >>>>>>>> echo >>>>>>>> './'`profile/profil.c >>>>>>>> {standard input}: Assembler messages: >>>>>>>> {standard input}:8: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:46: Error: suffix or operands invalid for `pop' >>>>>>>> {standard input}:80: Error: suffix or operands invalid for `call' >>>>>>>> {standard input}:84: Error: suffix or operands invalid for `call' >>>>>>>> {standard input}:141: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:170: Error: suffix or operands invalid for `pop' >>>>>>>> {standard input}:175: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:177: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:178: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:200: Error: suffix or operands invalid for `call' >>>>>>>> {standard input}:207: Error: suffix or operands invalid for `push' >>>>>>>> {standard input}:245: Error: suffix or operands invalid for `pop' >>>>>>>> {standard input}:277: Error: suffix or operands invalid for `call' >>>>>>>> {standard input}:281: Error: suffix or operands invalid for `call' >>>>>>>> make[2]: *** [profile/lib32_libgmon_a-profil.o] Error 1 >>>>>>>> >>>>>>>> Hello: >>>>>>>> the above error build with gcc-4_4-branch >>>>>>>> mingw-w64-cry >>>>>>>> I assue this is a gcc's bug? >>>>>>>> >>>>>>> oh this is with building multilib oiption if it matters >>>>>>> >>>>>> I don't understand, gcc was configured with multilib >>>>>> enable-targets=all, >>>>>> no error produced without m32 option this means gcc-4_4-branch >>>>>> does not >>>>>> support or binutils's problem? >>>>>> Anyone? >>>>>> >>>>>> >>>>> >>>>> Hi, >>>>> there is a high chance that binutils wasn't configured for multilib, >>>>> how did you configure binutils? >>>> It was configured with : >>>> --enable-multilib --enable-targets=x86_64-w64-mingw32,i686-w64-mingw32 >>>> objdump --help show this >>>> objdump: supported targets: pe-x86-64 pei-x86-64 elf64-x86-64 >>>> elf64-l1om elf64-little elf64-big elf32-little elf32-big pe-i386 >>>> pei-i386 elf32-i386 srec symbolsrec verilog tekhex binary ihex >>>> objdump: supported architectures: i386 i386:x86-64 i8086 i386:intel >>>> i386:x86-64:intel l1om l1om:intel >>>> I read "http://www.cadforte.com/wiki/index.php/How_to_build"; and >>>> pretty much followed the instructions. >>>> objdump on this object file which was compiled successfully >>>> lib32_libm_a-_libm_dummy.o: file format pe-x86-64 >>>> >>> Also ld --help output correctly showing >>> ld: supported targets: pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om >>> elf64-little elf64-big elf32-little elf32-big pe-i386 pei-i386 >>> elf32-i386 srec symbolsrec verilog tekhex binary ihex >>> ld: supported emulations: i386pep i386pe >>> >>> Is there something wrong with my build or gcc or mingw-w64-crt? >>> >>> What's the real difference between pe-x86-64 pei-x86-64? >>> >> >> Hi, >> >> I've just built the crt a few days ago without issues. PE and PEI are >> the executable format and object format used on Windows. >> >> It really looks like the assembler is not able to understand 32bit >> asm. BTW, ld != x86_64-w64-mingw32-ld. >> >> What does "x86_64-w64-mingw32-ld --help|grep supported\ targets" say? >> > x86_64-w64-mingw32-ld: supported targets: pe-x86-64 pei-x86-64 > elf64-x86-64 elf64-l1om elf64-little elf64-big elf32-little elf32-big > pe-i386 pei-i386 elf32-i386 srec symbolsrec verilog tekhex binary ihex > I have the PATH so ld is the actual x86_64-w64 target's ld >
[Adding mingw-w64-public back, my mail client dropped it] Hi, What does "x86_64-w64-mingw32-gcc -print-prog-name=as" say? I suspect the wrong "as" was called. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
