From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29902 invoked by alias); 12 Dec 2001 21:54:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 29829 invoked from network); 12 Dec 2001 21:54:35 -0000 Received: from unknown (HELO itdomain003.itdomain.net.au) (203.63.157.208) by sources.redhat.com with SMTP; 12 Dec 2001 21:54:35 -0000 Received: from lifelesswks ([144.137.123.92]) by itdomain003.itdomain.net.au with Microsoft SMTPSVC(5.0.2195.3779); Thu, 13 Dec 2001 08:54:34 +1100 Message-ID: <068801c18357$97c5a370$0200a8c0@lifelesswks> From: "Robert Collins" To: "Teun Burgers" , References: <3C17011D@freeler-webmail-01> <04ea01c18303$55406a70$0200a8c0@lifelesswks> <3C17B526.60915DD9@freeler.nl> Subject: Re: gcc -mno-cygwin creates cygwin executables! Date: Wed, 12 Dec 2001 14:01:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 12 Dec 2001 21:54:34.0425 (UTC) FILETIME=[95F3A290:01C18357] X-SW-Source: 2001-12/txt/msg00662.txt.bz2 ----- Original Message ----- From: "Teun Burgers" > 1) How about making libpthread.a a dummy library with just one .o file > with a dummy (empty) function? This does fix this particular > configure problem, but might have side effects since the pthread > symbols > are no longer in libpthread.a You already know the correct fix to this scenario. Patch ld to be able to act like gcc with -mno-cygwin. Please don't go look for solutions that are really just workarounds. > 2) include the pthread symbols in both libcygwin.a and libpthread.a? I will not support cygwin pthread functions linked statically. I should have said that before. Those functions both depend on cygwin and are depended on by cygwin. > Robert Collins wrote: > > > Hmm. Why not put the win32 api checks in the configure script ahead of > > pthread? > > What do you mean with that? Fix the configure script so that it checks for Win32 availability - and thus win32 thread functions - before pthreads. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/