25 июля 2014 г., в 8:05, Óscar Fuentes написал(а):
> klo uo writes:
>
>> I upgraded from 4.8.1 to 4.9.1 (x86_64-4.9.1-release-win32-seh-rt_v3-rev0)
>> and noticed that the package I used to build successfully, now fails.
>>
>> The package is latest hunspell-1.3.3 and it fails with libtool er
OK, I recreated logs.
Configure script outputs exact same log on command line for both MinGW
versions.
Make script errors as reported, and this is the diff file between 4.8.1 and
4.9.1 make outputs: https://gist.github.com/anonymous/a73e9d019fb2ff7d6900
Here is libtool file, generated by 4.9.1 poi
This just fix the ftw issue. But still have "%lld", mkdir, "GCC poison
strerror" issue on gcov.
You can following the build instructions at:
http://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/mingw-w64-doc/howto-build/mingw-w64-howto-build.txt
Regards,
Dongsheng
On Thu, Jul 24, 2014 at
klo uo writes:
> I upgraded from 4.8.1 to 4.9.1 (x86_64-4.9.1-release-win32-seh-rt_v3-rev0)
> and noticed that the package I used to build successfully, now fails.
>
> The package is latest hunspell-1.3.3 and it fails with libtool error
> (failing to match some quote on line 7000 or so).
>
> Rem
Hi,
I upgraded from 4.8.1 to 4.9.1 (x86_64-4.9.1-release-win32-seh-rt_v3-rev0)
and noticed that the package I used to build successfully, now fails.
The package is latest hunspell-1.3.3 and it fails with libtool error
(failing to match some quote on line 7000 or so).
Removing 4.9.1 and installi
"lh_mouse" writes:
> EDIT: since C99, reaching the } that terminates the main function returns a
> value of 0.
>
> 'The returned value is undefined' is not true. If the return value is used(in
> the case of main(),
> the host environment cares about it),
I already said that undefined behavior a