Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Herb Martin" <HerbM AT learnquick DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: ./configure and pthreads
Date:	Thu, 29 Sep 2005 10:35:29 -0500
MIME-Version:	1.0
In-Reply-To:	<Pine.CYG.4.58.0509291023420.2244@PC1163-8460-XP.flightsafety.com>
Message-ID:	<EINL4N7-000MWK-6Y@mail2.learnquick.com>
X-Sign-LQC:	HerbM AT learnquick DOT com/2005-09-29 10:35:33/<cygwin AT cygwin DOT com>=aykauhfa

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Brian Ford
> Sent: Thursday, September 29, 2005 10:26 AM
> > Sure I would love someone to just 'solve' this for me but 
> what is the 
> > most useful way to diagnose (or learn to diagnose) this problem so 
> > that I may create a more useful report?
> >
> > (Although a developer, I admit to being mostly ignorant of 
> > make/configure issues...but I can learn.)
> 
> Look in the build directory for the file config.log, search 
> for pthreads, and find out what failed.
> 
> Sounds like their pthread detection macro is broken.  I have 
> one that works fine on Cygwin.

Apparently (from a separate message on the DSPAM list)
they added -ldl and FreeBSD and (maybe) CygWin don't
have/use this?

Going to check now....

--
Herb 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -