On Tue, Dec 22, 2009 at 9:53 PM, Kai Tietz <[email protected]> wrote: > 2009/12/22 Alon Bar-Lev <[email protected]>: >> Hi, >> >> I think that i686-w64-mingw32 should be supported, right? >> At least it would be great if it is as this project is much more >> maintained and complete than mingw32. >> >> While trying to do so, I get the following... And indeed the >> declaration is duplicated. >> I tested both v1.0 and trunk snapshots, gcc is 4.4.2. >> >> x86_64-w64-mingw32 compiles OK. >> >> /var/tmp/cross/i686-w64-mingw32/portage/cross-i686-w64-mingw32/mingw64-runtime-20091222/work/sysroot/usr/i686-w64-mingw32/include/intrin.h:585: >> error: conflicting types for ‘_mm_shuffle_ps’ >> /usr/lib/gcc/i686-w64-mingw32/4.4.2/include/xmmintrin.h:716: note: >> previous definition of ‘_mm_shuffle_ps’ was here >> make[1]: *** [intrincs/lib32_libmingwex_a-readfsword.o] Error 1 >> make[1]: *** Waiting for unfinished jobs.... >> In file included from intrincs/readfsbyte.c:1: >> /var/tmp/cross/i686-w64-mingw32/portage/cross-i686-w64-mingw32/mingw64-runtime-20091222/work/sysroot/usr/i686-w64-mingw32/include/intrin.h:585: >> error: conflicting types for ‘_mm_shuffle_ps’ >> /usr/lib/gcc/i686-w64-mingw32/4.4.2/include/xmmintrin.h:716: note: >> previous definition of ‘_mm_shuffle_ps’ was here >> make[1]: *** [intrincs/lib32_libmingwex_a-readfsbyte.o] Error 1 >> In file included from intrincs/readfsdword.c:1: >> /var/tmp/cross/i686-w64-mingw32/portage/cross-i686-w64-mingw32/mingw64-runtime-20091222/work/sysroot/usr/i686-w64-mingw32/include/intrin.h:585: >> error: conflicting types for ‘_mm_shuffle_ps’ >> /usr/lib/gcc/i686-w64-mingw32/4.4.2/include/xmmintrin.h:716: note: >> previous definition of ‘_mm_shuffle_ps’ was here >> make[1]: *** [intrincs/lib32_libmingwex_a-readfsdword.o] Error 1 >> make[1]: Leaving directory >> `/var/tmp/cross/i686-w64-mingw32/portage/cross-i686-w64-mingw32/mingw64-runtime-20091222/work/trunk/mingw-w64-crt' >> make: *** [all] Error 2 >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Mingw-w64-public mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public >> > > Yes, i686 should be supported and I am curious about this warning, but > well, you are using 4.4.2 gcc. > I'll try to find out where this issue comes from and then prepare a > fix for this. > > Cheers, > Kai
Which gcc should I use? ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
