2013/9/23 Martin Mitáš <m...@morous.org>:
>>
>> P.S.
>> 32-bit:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-posix/sjlj/i686-4.8.1-release-posix-sjlj-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-posix/dwarf/i686-4.8.1-release-posix-dwarf-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-win32/sjlj/i686-4.8.1-release-win32-sjlj-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-win32/dwarf/i686-4.8.1-release-win32-dwarf-rev1.7z
>>
>> 64-bit:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.1/threads-posix/sjlj/x86_64-4.8.1-release-posix-sjlj-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.1/threads-posix/seh/x86_64-4.8.1-release-posix-seh-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.1/threads-win32/sjlj/x86_64-4.8.1-release-win32-sjlj-rev1.7z
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.1/threads-win32/seh/x86_64-4.8.1-release-win32-seh-rev1.7z
>>
>
> I would like to highlight these builds expose the bug #346
> (http://sourceforge.net/p/mingw-w64/bugs/346/).
>
Yes. It fixed in mingw-w64 repository after rev1.
Tomorrow I plan to upload rev2 that based on latest minw-w64 runtime
v3 that resolve this issue.

> As a side note, the filenames make me wonder whether having 4.8.1 rev1
> from mingw-w64 being different from 4.8.1 rev1 on mingw-builds project
> shall lead to confusion of people (and core project developers too, when
> you get bug reports etc.) or not. Was this considered?
>
Yes. This is can confuse users. But we start revision numeration from
the zero when moving to mingw-w64 project. Now we don't plan to update
toolchains on mingw-builds project.

> Last but not least, I've got an impression from the recent mailing list
> activity that these builds probably use the CRT from mingw-w64 stable
> 3.0, right? Shouldn't be the versioning/file_naming scheme updated to
> reflect also what mingw-w64 branch/version is in it?
>
Rev2 will be based on stable v3. Rev0 and rev1 are based on pre-v3
trunk version.
Starting rev2 I 'm add rt_v3(or v4 for trunk) into toolchain archive name.

Regards,
Alexey.

> (But do not take my critics too heavily. I see the decision to join
> mingw-w64 and mingw-builds as a step in the right direction and I am
> looking forward the bright future. Lets the synergies grow :-)
>
> Martin
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to