This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Yaakov S (Cygwin Ports) wrote:After doing some experimentation, it looks like this isn't a specific problem with gvim, but is common to gtk2 apps, e.g.:
$ CYGWIN= gcolor2 Bad system call
$ gcolor2 [runs]
I don't think that should be necessary, except in very trying cases like, say, a database like postgresql. So, whatever is using SYSV shared memory in this scenario, it shouldn't. The fact that I can start
gvim on local Xmingw server but not on a remote X server shows,
that SYSV shared memory can't be a necessity.
Gerrit?
Yes maybe, need to take a look at the configure and build logs though.
Yes, --enable-shm is default=yes. I rebuild now the pending 2.6.10 release with --enable-shm=no and upload later this day.
Gerrit -- =^..^=
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |