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(' ');

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 Cygwin version that

1.7.0-58 fixes fork crash in 1.7-compiled app running on 1.5

-58 fixed a repeatable crash I was seeing in fork on every machine on which I ran a particular big hairy application (http://software.jessies.org/terminator). Nothing new there, so I only spam you with my thanks because the machines in question were all running 1.5, though the executable was compi

Re: Creating a dll in cygwin for use with jni without -mno-cygwin

> The problem here is that you're loading the Cygwin1.dll library > dynamically, as opposed to linking against it normally. (Depending on exactly what you're trying to do, another approach can be to use a Cygwin-based executable to launch Java. There's more information about how to do that, incl

Re: faked inode numbers on network drives

Martin Koeppe wrote: >> (samba reports the device number as low part of the inode number, and >> the real ext2 fs inode number as high part, which is bad for >> interix/sfu, as it only shows the low part as inode number. I just >> reported this as samba bug 3287, see >> https://bugzilla.samba.o

Re:JNI and cygwin

> I need terminal and ncurses support and I have a JNI > layer that interacts with "curses" functions. Me too (for http://www.jessies.org/~enh/software/terminator/). > I have problems using the cygwin libraries with Java > VM. I had problems too - probably the same ones. They're discussed at:

less-381-1: doesn't use terminfo?

Is it deliberate and desirable to have less(1) not be terminfo-aware? Splitting the terminal capability database into several files certainly makes it easy to install the entry for a new terminal type. Background: I've been porting a terminal emulator (http://www.jessies.org/~enh/software/termina