Please don't resolve native symbolic links in cygwin_conv_path

If a POSIX path supplied to cygwin_conv_path ends in a symbolic link, the returned path refers to the target of that link. Normally, that's a good thing because native programs can't understand Cygwin links. But this behavior is unwanted when we're looking at a *native* symbolic link that all progr

Re: Mingw headers broken with _WIN32_WINNT = 0x601 (Win7)

Thanks --- much appreciated. On Thu, Jan 6, 2011 at 3:35 PM, JonY wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 1/7/2011 07:20, Daniel Colascione wrote: >> If we have this program >> >> #define _WIN32_WINNT 0x601 >> #include >> >> int main() {} >> >> >> And try to compile it li

Re: New version of w3m 0.5.2 Crashes - GDB help needed

Bob Heckel writes: > On Wed, Jan 5, 2011 at 16:22, Christopher Faylor wrote: >> On Wed, Jan 05, 2011 at 04:16:37PM -0500, nyc4bosaol.com wrote: >>>nyc4bosaol.com writes: >>> >>>Bob created a debug version of w3m for me. >>> >>>Here's what I see: >>> >>>The crash occurs when doin a `strncmp' in cy

Re: Mingw headers broken with _WIN32_WINNT = 0x601 (Win7)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/7/2011 07:20, Daniel Colascione wrote: > If we have this program > > #define _WIN32_WINNT 0x601 > #include > > int main() {} > > > And try to compile it like so, > > x86_64-w64-mingw32-gcc hello.c > > The compile fails with > > In file inc

Mingw headers broken with _WIN32_WINNT = 0x601 (Win7)

If we have this program #define _WIN32_WINNT 0x601 #include int main() {} And try to compile it like so, x86_64-w64-mingw32-gcc hello.c The compile fails with In file included from /usr/x86_64-w64-mingw32/sys-root/mingw/include/windows.h:86:0, from hello.c:2: /usr/x86_64-w6

Cygwin, VSS snapshots and Rsync

Hi, I don’t know if the problem is related to Cygwin or Windows, but I thought It was worth asking… I have no problem to use Rsync under Cygwin (Windows 7) on normal conditions, for example to copy one file on a remote Ubuntu server. Things get complicated when I want to copy open files. To perf

Re: gcc: stable 4.5 soon?

Dave, Our GCC 4.5 packages has been "experimental" since August. I have been running 4.5.1, and now 4.5.2, with only slight modifications to your patchset since then[1], including an important fix for libgcj[2]. My latest changes are in Ports git[3]. Since I have been using 4.5 for so long, I f