Re: [Mingw-w64-public] x64 MSVC import librries

2015-03-18 Thread Vadim Chugunov
Thanks! Sorry for the wrong mailing list, but looks like things worked out in the end :) Are there any mingw builders, who track the master branch in binutils? Vadim On Wed, Mar 18, 2015 at 9:38 AM, Kai Tietz wrote: > 2015-03-18 17:19 GMT+01:00 Ruben Van Boxem : > > 2015-03-18 16:28 GMT+01:0

Re: [Mingw-w64-public] x64 MSVC import librries

2015-03-18 Thread Kai Tietz
2015-03-18 17:19 GMT+01:00 Ruben Van Boxem : > 2015-03-18 16:28 GMT+01:00 Derek Buitenhuis : >> >> On 3/17/2015 11:27 PM, Vadim Chugunov wrote: >> > I think I am bumping into the issue described here: >> > https://sourceware.org/bugzilla/show_bug.cgi?id=16598. The bug also has a >> > patch attache

Re: [Mingw-w64-public] x64 MSVC import librries

2015-03-18 Thread Ruben Van Boxem
2015-03-18 16:28 GMT+01:00 Derek Buitenhuis : > On 3/17/2015 11:27 PM, Vadim Chugunov wrote: > > I think I am bumping into the issue described here: > https://sourceware.org/bugzilla/show_bug.cgi?id=16598. The bug also has > a patch attached. What would it take to get someone to merge it? > > Th

Re: [Mingw-w64-public] x64 MSVC import librries

2015-03-18 Thread Derek Buitenhuis
On 3/17/2015 11:27 PM, Vadim Chugunov wrote: > I think I am bumping into the issue described here: > https://sourceware.org/bugzilla/show_bug.cgi?id=16598. The bug also has a > patch attached. What would it take to get someone to merge it? This is a patch to binutils, and not MinGW, and thus t

Re: [Mingw-w64-public] backports for v4.x ?

2015-03-18 Thread Ozkan Sezer
On 3/18/15, Kai Tietz wrote: > 2015-03-18 15:50 GMT+01:00 Ozkan Sezer : >> The following three commits look like they are condidates >> for cherry-pick'ing into v4.x. Should we do it? >> >> FOR v4.x: commit 7b41fe36c0be9a14bf1d82c74dfd00f20370e8d7 >> Author: Jacek Caban >> Date: Fri Jan 30 11:

Re: [Mingw-w64-public] backports for v4.x ?

2015-03-18 Thread Kai Tietz
2015-03-18 15:50 GMT+01:00 Ozkan Sezer : > The following three commits look like they are condidates > for cherry-pick'ing into v4.x. Should we do it? > > FOR v4.x: commit 7b41fe36c0be9a14bf1d82c74dfd00f20370e8d7 > Author: Jacek Caban > Date: Fri Jan 30 11:16:50 2015 +0100 > time.h: Ensure that

[Mingw-w64-public] backports for v4.x ?

2015-03-18 Thread Ozkan Sezer
The following three commits look like they are condidates for cherry-pick'ing into v4.x. Should we do it? FOR v4.x: commit 7b41fe36c0be9a14bf1d82c74dfd00f20370e8d7 Author: Jacek Caban Date: Fri Jan 30 11:16:50 2015 +0100 time.h: Ensure that _POSIX_THREAD_SAFE_FUNCTIONS is defined if we declare

Re: [Mingw-w64-public] Missing prerequisites in shlobj.h

2015-03-18 Thread LRN
On 18.03.2015 3:37, LRN wrote: > In file included from ../../poppler-0.30.0/poppler/GlobalParams.cc:59:0: > F:/e41/mingw/include/shlobj.h:37:3: error: 'EXTERN_C' does not name a type >SHFOLDERAPI SHGetFolderPathW (HWND hwnd, int csidl, HANDLE hToken, DWORD > dwFlags, LPWSTR pszPath); > > ... >