Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3AEB90E8.9000000@itdomain.com.au>
Date: Sun, 29 Apr 2001 13:56:24 +1000
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.18pre21 i686; en-US; m18) Gecko/20001103
X-Accept-Language: en
MIME-Version: 1.0
To: "kern AT sibbald DOT com" <kern AT sibbald DOT com>
CC: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Re: Some comments about the current release
References: <01C0CFC8 DOT 2F9E82A0 DOT kern AT sibbald DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2001 03:51:57.0773 (UTC) FILETIME=[BCFFDFD0:01C0D05F]

Kern Sibbald wrote:

> Hello,
> 
> In loading the current Cygwin software (dll 1.3.1
> and others), in addition to the cygwin1.dll performance
> degradation, while loading the latest version of all
> the other files, I ran into the following problems:
> 
> <skip>
> 3. Thanks for adding pthreads support. It works!  However,
> it would be really nice if you provided a null 
> libpthreads.a library so that we don't have to modify all
> our Makefiles.


Pthreads support was present before. It's just a little more substantial 
now. Your makefiles are broken if they assume that libpthreads.a is the 
library name. On different platforms I have seen
nothing (as cygwin does - libc provides pthread support)
libpthread.a
libc_r.a

I suggest you fix your makefiles. (Hint: autoconf is a wonderful tool).

> 4. I was including <winsock2.h> in a bunch of header files
> in my .cpp programs which are strictly Windows (no Unix
> stuff) and I got lots of warning messages, which were 
> annoying. In my case, I solved the problem by removing
> the include of <winsock2.h> as it wasn't really needed,
> but it seems to me that there is a problem here that
> needs some attention.

If they are "strictly windows" you might want to look at using mingw to 
build them instead.

Rob


> Best regards,
> 
> Kern Sibbald
> 
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 




--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple