On Tue, Aug 2, 2011 at 14:00, Farkas Levente <[email protected]> wrote: > On 08/02/2011 01:41 PM, Luca Barbato wrote: >> On 8/2/11 10:43 AM, Farkas Levente wrote: >>> On Mon, Aug 1, 2011 at 14:55, Luca Barbato<[email protected]> wrote: >>>> qlist -Iv yasm mingw >>>> cross-i686-w64-mingw32/binutils-2.21 >>>> cross-i686-w64-mingw32/gcc-4.5.2 >>>> cross-i686-w64-mingw32/mingw64-runtime-20101003 >>>> cross-mingw32/binutils-2.21 >>>> cross-mingw32/gcc-4.5.2 >>>> cross-mingw32/mingw-runtime-3.18 >>>> cross-mingw32/w32api-3.15 >>>> cross-x86_64-w64-mingw32/binutils-2.21 >>>> cross-x86_64-w64-mingw32/gcc-4.5.2 >>>> cross-x86_64-w64-mingw32/mingw64-runtime-20101003 >>>> dev-lang/yasm-1.1.0-r1 >>>> >>>> Those are my versions for the toolchains not sure how much it helps. >>> >>> do you hvae bot mingw32 and i686-w64-mingw32 installed? which one do >>> you use to build http://win32.libav.org/win32/ ? >> >> mingw32 , the i686-mingw64 is used to test pthreads support. > > do you mean that these pacakges: > http://win32.libav.org/win32-pthreads/ > build with these packages: > cross-i686-w64-mingw32/binutils-2.21 > cross-i686-w64-mingw32/gcc-4.5.2 > cross-i686-w64-mingw32/mingw64-runtime-20101003
finally it's turn out that gcc-4.6.1 and gcc-4.6.2 generate code which segfault while gcc-4.5.3 is running. i don't know whether it's a gcc bug or libav (the strange thing is that everything else is working with gcc-4.6.x). may be it'd be useful to find the reason why. i already send a long mail about it to mingw64 and fedora mingw list: http://lists.fedoraproject.org/pipermail/mingw/2011-August/004087.html ps. anyway because the windows build is not working with the latest release, it's high time for a new release (and also because of the rename). regards. -- Levente "Si vis pacem para bellum!" _______________________________________________ libav-tools mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-tools
