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 Message-ID: <005801c28fe7$99b309a0$78d96f83@pomello> From: "Max Bowsher" To: "Markus Gerwinski" , Cc: References: <20021119160845.GC4923@leia.local> Subject: Re: Conflict between libcygwin.a and GCC core libraries Date: Tue, 19 Nov 2002 16:20:39 -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-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Markus Gerwinski wrote: > I'm currently trying to compile GPA (s. > http://www.gnupg.org/gpa.html) on Cygwin. To get it up and running, > first of all I had to insert "-mno-cygwin > -mms-bitfields" into the compiler options. If you add -mno-cygwin, then you are trying to compile GPA for MinGW, not Cygwin. > After changing some more > stuff in the makefiles, compiling runs fine now, but linking still > causes trouble. First, I got a lot of `undefined references' to > functions as basic as `__assert'. To get rid of them, I included > "-lcygwin" by hand into the linker options. Aaargh! First you tell gcc to not use cygwin, then you tell it to sort-of use cygwin. No wonder its confused! Solution: Don't do that. Do you actually intend to compile GPA for MinGW or Cygwin? If Cygwin, drop the -mno-cygwin. If MinGW, make sure the gcc-mingw package is installed. Max. -- 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/