11 июня 2014 г., в 6:50, Jon написал(а):
>
> On Mon, Jun 9, 2014 at 10:33 AM, Jon wrote:
>
> On Mon, Jun 9, 2014 at 10:20 AM, Jon wrote:
>
> On Sat, Jun 7, 2014 at 2:06 PM, Jon wrote:
> The 4.8.x series changed its default behavior re: libgcc linking when on
> Windows
>
> http://gcc.gnu.
On Mon, Jun 9, 2014 at 10:33 AM, Jon wrote:
>
> On Mon, Jun 9, 2014 at 10:20 AM, Jon wrote:
>
>>
>> On Sat, Jun 7, 2014 at 2:06 PM, Jon wrote:
>>
>>> The 4.8.x series changed its default behavior re: libgcc linking when on
>>> Windows
>>>
>>> http://gcc.gnu.org/gcc-4.8/changes.html#windows
>>>
On Mon, Jun 9, 2014 at 10:20 AM, Jon wrote:
>
> On Sat, Jun 7, 2014 at 2:06 PM, Jon wrote:
>
>> The 4.8.x series changed its default behavior re: libgcc linking when on
>> Windows
>>
>> http://gcc.gnu.org/gcc-4.8/changes.html#windows
>>
>> I'm testing with my environment to confirm 4.9.x default
On Sat, Jun 7, 2014 at 2:06 PM, Jon wrote:
> The 4.8.x series changed its default behavior re: libgcc linking when on
> Windows
>
> http://gcc.gnu.org/gcc-4.8/changes.html#windows
>
> I'm testing with my environment to confirm 4.9.x default libgcc linking
> behavior (for both exes and dlls) for t
The 4.8.x series changed its default behavior re: libgcc linking when on
Windows
http://gcc.gnu.org/gcc-4.8/changes.html#windows
I'm testing with my environment to confirm 4.9.x default libgcc linking
behavior (for both exes and dlls) for the following two toolchains because
the GCC 4.9 changelog