public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Mumit Khan <khan@nanotech.wisc.edu>
To: Love <lha@stacken.kth.se>
Cc: pthreads-win32@sourceware.cygnus.com
Subject: Re: Cygwin confusion
Date: Tue, 07 Dec 1999 12:06:00 -0000	[thread overview]
Message-ID: <199912072005.OAA00918@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <199912052120.WAA03264@hummel.e.kth.se>

Love <lha@stacken.kth.se> writes:
> 
> Some comments to make pthreads-win32 compile on cygwin, there is no
> erase command on my system, please autoconf for it or use rm.
> 
> AC_CHECK_HEADER never adds the HAVE_SIGNAL_H to the config.h,
> AC_CHECK_HEADERS will do.

Correct.

> After that I don't really know what to do, there is a lot of __MINGW32__ and 
> __MSVCRT__, but where do Cygwin fit in ?

Some of the changes are superceded by my patch for mingw, so not quite
applicable. 

Cygwin doesn't support threaded code, so nobody has bothered to do much 
with it. This is not true for development snapshots, which you can build
with --enable-threads, but there are other issues (gcc must be built with
thread-safety, and then there is a small chicken and egg problem); Cygwin
also provides a minimal pthreads implementation with built thread enabled,
but it's quite inadequate at the moment.

The configur'y in pthreads is badly in need of a rewrite, and I'll do that
at some point. Currently, most of the work is being down with VC++, so
it's probably not getting stressed. I have rewritten most of the autoconf
mechanism, but I want to wait until my last patch is accepted before
submitting these. 

> Dunno what to do about that DWORD change.

It's about the same thing for 32-bit w32api in the context of this 
particular piece of code, so makes no difference for now.

Regards,
Mumit


           reply	other threads:[~1999-12-07 12:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <199912052120.WAA03264@hummel.e.kth.se>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199912072005.OAA00918@mercury.xraylith.wisc.edu \
    --to=khan@nanotech.wisc.edu \
    --cc=lha@stacken.kth.se \
    --cc=pthreads-win32@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).