RE: Questionalbe command line defines for Cygwin/XFree86

[Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>]

OK, I will give it a shot :-)

Thanks
Suhaib


> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Sunday, April 08, 2001 9:01 PM
> To: Suhaib Siddiqi; Harold Hunt ; Cygx (E-mail) 
> Subject: RE: Questionalbe command line defines for Cygwin/XFree86
> 
> 
> 
> 
> > -----Original Message-----
> > From: Suhaib Siddiqi [mailto:ssiddiqi@inspirepharm.com]
> > Sent: Monday, April 09, 2001 10:41 AM
> > To: Robert Collins; 'Harold Hunt '; 'Cygx (E-mail) '
> > Subject: RE: Questionalbe command line defines for Cygwin/XFree86
> > 
> > 
> >  ThreadSafeX API needs a complete pthread library.  Do we 
> > have pthread by
> > default in Cygwin?  My understanding is no, and I do not want 
> > to enable
> > something on custom DLLs because that will create a support 
> nightmare.
> > 
> > Suhaib
> > 
> 
> We do have pthread by default in cygwin. It's a wrapper around native
> win32 threads. It's not 100% complete, but I don't have the time to
> simply write everything, nor the time to fix problems porting code
> _other than_ the thread using code. So The deal I've offered on the
> cygwin lists (including this one) is that you tell me what 
> functions you
> need that are missing (check a current snapshot or better yet cygwin
> CVS) and I'll write them. There aren't many missing now. There's no
> library needed when linked in pthread code, it's part of libcygwin1.a.
> 
> What I'm suggesting is you try and build with thread support, report
> back what happened, and I'll fix that. When that's fixed you 
> try again,
> and I fix again. When it's all working, the code will 
> (hopefully :]) get
> committed to cygwin1.dll and be available as a snapshot release. When
> the next official release gets rolled, you can release an updated
> XFree86 using ThreadSafeX.
> 
> Rob
> 
> 
> > -----Original Message-----
> > From: Robert Collins
> > To: Harold Hunt; Cygx (E-mail)
> > Sent: 4/8/2001 8:20 PM
> > Subject: RE: Questionalbe command line defines for Cygwin/XFree86
> > 
> > If you guys can provide some pointers on missing thread code I will
> > endeavour to supply it. FWIW I have a threadglib running here...
> > 
> > Rob
> > 
> >  
> > 
> > > -----Original Message-----
> > > From: Harold Hunt [mailto:huntharo@msu.edu]
> > > Sent: Monday, April 09, 2001 10:18 AM
> > > To: Cygx (E-mail)
> > > Subject: Questionalbe command line defines for Cygwin/XFree86
> > > 
> > > 
> > > In debugging the freezes and crashes, I've noticed a couple 
> > > of symbols that
> > > are defined on the command line.  I don't really like the 
> > > looks of any of
> > > these, and I've tried to get rid of a few of them, but I'd 
> > > like input on
> > > what they do, and whether other people think we need them.
> > > 
> > > -DBUILDDEBUG
> > > 	Happens even when not doing a debug build.
> > > -DXTEST
> > > 	There is some code in WaitFor.c that runs when
> > > 	XTESTEXT1 is defined; I'm wondering if XTEST
> > > 	causes XTESTEXT1 to become defined.
> > > -DSCREENSAVER
> > > 	We can't really have a screen saver, so why
> > > 	would we need this?  This could possibly
> > > 	be affecting the timeout value in WaitFor.c.
> > > -D_REENTRANT
> > > 	Cygwin.cf defines ThreadedX and HasThreadSafeAPI
> > > 	to NO, so what are we allowing to be reentrant?
> > > 
> > > Input on this, and our pointers as to how to undefine these 
> > > symbols would be
> > > appreciated.
> > > 
> > > Harold
> > > 
> > > 
> > 
>