On 08/08/2011 02:56 PM, Ozkan Sezer wrote: > On Mon, Aug 8, 2011 at 3:02 PM, Farkas Levente <lfar...@lfarkas.org> wrote: >> On 08/08/2011 12:49 PM, Kai Tietz wrote: >>> I agree that we need to setup a fixed way how releases need to be >>> done. I think a time-based schedule for this could be a good >>> approach. As in general our runtime isn't necessarly strict bound to >>> a specific gcc or binutils version. Most dependencies are here >>> present between gcc and binutils version, but mingw-w64 tries to >>> handle all valid combinations of them. >> >> the main reason why i come up with this whole thread was that we try to >> package w64 for fedora and rhel. after i build many packages it's turn >> out that libav (aka ffmpeg) was build clean but segfault immediately >> when build with w64. while if i build with mingw32 then it's working. > > Is the failing one an x86 build or an x64 build?
x86. > Any interesting warnings from the build process? nothing. as i wrote i'll write more detail about it, but it's currently not our highest priority:-( -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
