Re: cygwin_create_path

On Jan 3 21:22, Andy Koppe wrote: > 2010/1/3 Andy Koppe: > > I'm having a spot of trouble changing mkshortcut to use the > > wchar_t-enabled cygwin_create_path instead of the deprecated > > cygwin_conv_to_full_win32_path & co. When converting to a Windows path >

Re: cygwin_create_path

2010/1/3 Andy Koppe: > I'm having a spot of trouble changing mkshortcut to use the > wchar_t-enabled cygwin_create_path instead of the deprecated > cygwin_conv_to_full_win32_path & co. When converting to a Windows path > using CCP_POSIX_TO_WIN_W, the result is a path starti

cygwin_create_path

I'm having a spot of trouble changing mkshortcut to use the wchar_t-enabled cygwin_create_path instead of the deprecated cygwin_conv_to_full_win32_path & co. When converting to a Windows path using CCP_POSIX_TO_WIN_W, the result is a path starting with "\\?\", e.g. "\\?\C

Re: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63

On Sun, Nov 15, 2009 at 02:53:24PM -0800, Martin Dorey wrote: >>Before the reloc changes, you'd already get an error if your program >>used ctype functions. > >Thinking it might be useful to get the error messages into the >googlotron, I tried to demonstrate this with little programs like this: > >

Re: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63

2009/11/15 Martin Dorey: >> Before the reloc changes, you'd already get an error if >> your program used ctype functions. > > Thinking it might be useful to get the error messages into the googlotron, I > tried to demonstrate this with little programs like this: > > $ cat /tmp/ctype.c > #include

RE: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63

> Before the reloc changes, you'd already get an error if > your program used ctype functions. Thinking it might be useful to get the error messages into the googlotron, I tried to demonstrate this with little programs like this: $ cat /tmp/ctype.c #include int main() { return tolower(' ');

Re: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63

2009/11/15 Martin Dorey: > Linking a C program using 1.7.0-63 or 1.7.0-64 causes this runtime error when > attempting to run the program on Cygwin 1.5: > > "The procedure entry point cygwin_create_path could not be located in the > dynamic link library cygwin1.dll". &g

cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63

Linking a C program using 1.7.0-63 or 1.7.0-64 causes this runtime error when attempting to run the program on Cygwin 1.5: "The procedure entry point cygwin_create_path could not be located in the dynamic link library cygwin1.dll". This happens with gcc-3 or gcc-4 - it's the