> 2012/9/24 Ozkan Sezer <seze...@gmail.com> > > > On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem > > <vanboxem.ru...@gmail.com> wrote: > > > 2012/9/24 Jon <jon.for...@gmail.com> > > >> > > >> > > fyi...the following libuv build fail still exists in > > >> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z` > > >> > > > > >> > > > >> > Yes, that's to be expected. There was no new tagged MinGW-w64 release. > > >> > The > > >> > previous easy fix still applies. > > >> > > > >> > Ruben > > >> > > >> Yes, using tagged vs. non-tagged is an interesting call. > > > > > > > > > THat's what a "release" version usually implies. This is a choice I make > > to > > > keep things clear. I'm also thinking about using gdb/binutils release > > > versions, even if it would only lead to more consistency. > > > > > >> > > >> But I also don't like wasting brain cells remembering lists-o-easy-fixes > > >> per toolchain, or your toolchain currently being the odd man out with > > code > > >> like that in a library such as libuv. > > >> > > >> > > >> mingw-builds 4.7.2: PASS > > >> tdm 4.7.1: PASS > > >> mingw 4.6.2: PASS > > >> rubenvb 4.7.2: FAIL > > >> > > > > > > All these use either the SVN v2.x or trunk MinGW-w64. I chose not to. > > > Neither will any Linux distro providing MinGW-w64. Although those might > > > backport patches if they really want to. I am not forcing you to abandon > > > your previously working/fixed toolchain. You can even just copy over all > > of > > > mingw64/x86_64-w64-mingw32 or mingw32/i686-w64-mingw32 because that part > > has > > > not changed since the previous build. > > > > > >> > > >> I've happily used your builds for awhile now as my reference MinGW-w64 > > >> toolchain. Perhaps in the future when you guys see similar issues that > > >> impact well known libraries, a patch MinGW-w64 release can be quickly > > tagged > > >> as a way of helping downstream integrators release updates in a non > > ad-hoc > > >> manner. > > > > > > > > > I understand, and this happens regularly, just not always. Stable tags > > can't > > > be updated each time a specific fix has landed. For every project in the > > > world it takes more than one fix to release a new version. I will build > > an > > > update package or provide a new build as soon as possible after this > > > happens. > > > > > > Please use a toolchain that works for you. And update minor versions only > > > when you need to. > > > > > > Ruben > > > > > > > FWIW, I just tagged and released v1.0.7 and v2.0.7 mingw-w64 headers and > > crt. > > > > I had a feeling this would happen :P > > I am uploading updated mingw-w64 v2.0.7 update packages "update" on > Sourceforge: > sourceforge.net/projects/mingw-w64/files/Toolchains targetting > Win64/Personal Builds/rubenvb/update/ > sourceforge.net/projects/mingw-w64/files/Toolchains targetting > Win32/Personal Builds/rubenvb/update/ > > Just extract and overwrite. > > Enjoy,
Fabulous. I'm off to confirm my automated toolchain integration scripts can take advantage of this between-release-update awesomeness :) It doesn't get said as often as it should, but a huge THANK YOU to those of you who donate their time and energy to make these toolchains (rubenvb, mingw-builds, tdm, mingw) possible, work well, and add so much value. Selecting tags/commits/versions that work well together is no small task. Without your continued efforts, downstream toolchain integration like the following wouldn't be so easy: https://github.com/oneclick/rubyinstaller/blob/master/config/compilers/mingw64.rb#L3-36 https://github.com/oneclick/rubyinstaller/blob/master/config/compilers/tdm_mingw.rb#L3-44 https://github.com/oneclick/rubyinstaller/blob/master/config/compilers/mingwbuilds.rb#L3-36 I am grateful. Jon --- Fail fast. Fail often. Fail publicly. Learn. Adapt. Repeat. http://thecodeshop.github.com | http://jonforums.github.com/ twitter: @jonforums ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
