This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: cygwin with --disable-threadsafe
- To: <cygwin-developers at cygwin dot com>
- Subject: RE: cygwin with --disable-threadsafe
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Wed, 11 Apr 2001 14:08:57 +1000
- Thread-Index: AcDCPD2TtuiqPKsXThCmgWshklZ4igAAMWxg
- Thread-Topic: cygwin with --disable-threadsafe
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Wednesday, April 11, 2001 1:49 PM
> To: cygwin-developers@cygwin.com
> Subject: Re: cygwin with --disable-threadsafe
>
>
> On Wed, Apr 11, 2001 at 11:06:42AM +1000, Robert Collins wrote:
> >Following up on my questions about @PTH_ALLOW@ I tried build
> cygwin with
> >--disable-threadsafe. It didn't build - pinfo and signal.h
> appeared to
> >be the main culprits.
> >
> >Have I broken something with my changes (I haven't removed the stub
> >functions that are under discussion yet), or is it currently
> broken? And
> >yes I plan to test it, but I may have something wrong here
> so an outside
> >reference point is useful.
>
> It looks like Cygwin doesn't even build with
> --disable-threadsafe anymore.
> I don't think this is a big deal and I doubt that it has
> anything to do
> with your changes. I guess I should just get rid of the
> option entirely.
>
> So, we can forget about the PTH_ALLOW kludge.
Should I remove that kludge and the #ifdef MT_SAFE stuff at the same
time?
> Sorry for not realizing this sooner.
No Worries. It's not like pthreads has been under active development :]
> cgf
>