Re: Fwd: failure notice

2016-01-12 Thread Tom Kacvinsky
16 at 1:43 PM, Tom Kacvinsky wrote: > On Tue, Dec 22, 2015 at 10:34 AM, Tom Kacvinsky > wrote: >> It turns out we are using the 32 bit version of cygwin, so I am going >> to try with 64 bit cygwin and the latest possible version and see how >> I fare. > > Happens with

Re: Fwd: failure notice

2016-01-04 Thread Tom Kacvinsky
On Tue, Dec 22, 2015 at 10:34 AM, Tom Kacvinsky wrote: > It turns out we are using the 32 bit version of cygwin, so I am going > to try with 64 bit cygwin and the latest possible version and see how > I fare. Happens with both 32 and 64 bit cygwin. I'm out of ideas. The develop

Re: Fwd: failure notice

2015-12-22 Thread Tom Kacvinsky
It turns out we are using the 32 bit version of cygwin, so I am going to try with 64 bit cygwin and the latest possible version and see how I fare. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.

Re: Fwd: failure notice

2015-12-21 Thread Tom Kacvinsky
On Tue, Dec 8, 2015 at 1:57 PM, Tom Kacvinsky wrote: > On Tue, Dec 8, 2015 at 11:55 AM, Tom Kacvinsky > wrote: >> On Tue, Dec 8, 2015 at 11:49 AM, Jon Turney >> wrote: >>> On 07/12/2015 16:17, Tom Kacvinsky wrote: >>>> >>>> On Mon, Dec 7, 20

Re: Fwd: failure notice

2015-12-08 Thread Tom Kacvinsky
On Tue, Dec 8, 2015 at 11:55 AM, Tom Kacvinsky wrote: > On Tue, Dec 8, 2015 at 11:49 AM, Jon Turney > wrote: >> On 07/12/2015 16:17, Tom Kacvinsky wrote: >>> >>> On Mon, Dec 7, 2015 at 10:24 AM, Tom Kacvinsky wrote: >>>> >>>> On Mon, Dec 7,

Re: Fwd: failure notice

2015-12-08 Thread Tom Kacvinsky
On Tue, Dec 8, 2015 at 11:49 AM, Jon Turney wrote: > On 07/12/2015 16:17, Tom Kacvinsky wrote: >> >> On Mon, Dec 7, 2015 at 10:24 AM, Tom Kacvinsky wrote: >>> >>> On Mon, Dec 7, 2015 at 10:19 AM, Jon Turney wrote: >>>> >>>> On 04/1

Re: Fwd: failure notice

2015-12-07 Thread Tom Kacvinsky
On Mon, Dec 7, 2015 at 10:24 AM, Tom Kacvinsky wrote: > On Mon, Dec 7, 2015 at 10:19 AM, Jon Turney > wrote: >> On 04/12/2015 14:20, Tom Kacvinsky wrote: >>> >>> Hi, >>> >>> We have an interesting problem whereby an Linux X client application >

Re: Fwd: failure notice

2015-12-07 Thread Tom Kacvinsky
On Mon, Dec 7, 2015 at 10:19 AM, Jon Turney wrote: > On 04/12/2015 14:20, Tom Kacvinsky wrote: >> >> Hi, >> >> We have an interesting problem whereby an Linux X client application >> crashes when running the X server on cygwin. We have a reproducer >>

Re: failure notice

2015-12-07 Thread Tom Kacvinsky
Hi. On Fri, Dec 4, 2015 at 9:20 AM, Tom Kacvinsky wrote: > Hi, > > We have an interesting problem whereby an Linux X client application > crashes when running the X server on cygwin. We have a reproducer > for the problem, but it is a Qt example application stored in a tarba

Fwd: failure notice

2015-12-04 Thread Tom Kacvinsky
Hi, We have an interesting problem whereby an Linux X client application crashes when running the X server on cygwin. We have a reproducer for the problem, but it is a Qt example application stored in a tarball. We have gathered the other information that would typically be requested. I just nee

Re: rpc/types.h: No such file or directory

2015-05-19 Thread Tom Kacvinsky
You need to set CFLAGS. And CXXFLAGS, too > On May 19, 2015, at 12:26, Gery . wrote: > > Thanks, however it didn't work if I put it in the install_makefiles or > .bashrc: > > # Required parameters: > $MBSYSTEM_HOME = "/usr/local/mbsystem"; > $OS = "LINUX"; > $CFLAGS = "-Wall -g -I/usr/X11/i

Fwd: Compatibility of binaries built with one version of cygwin with other versions of cygwin

2015-03-27 Thread Tom Kacvinsky
Question: if I build an executable/shared library on one version of cygwin, is it guaranteed to work on later versions of cygwin, or is that not recommended? I learned the difficult way that building on one version and running on an earlier version doesn't work. My binaries are based on C++ code