Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Herb Martin" To: Subject: RE: ./configure and pthreads Date: Thu, 29 Sep 2005 10:35:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-Sign-LQC: HerbM@learnquick.com/2005-09-29 10:35:33/=aykauhfa > -----Original Message----- > From: cygwin-owner@cygwin.com > [mailto:cygwin-owner@cygwin.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/