Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=iso-8859-1 X-Priority: 3 Date: Wed, 20 Nov 2002 10:01:06 +0000 From: Max Bowsher To: markus AT gerwinski DOT de, cygwin AT cygwin DOT com Subject: Re: Conflict between libcygwin.a and GCC core libraries Message-Id: > >Subject: Re: Conflict between libcygwin.a and GCC core libraries > From: Markus Gerwinski > Date: Wed, 20 Nov 2002 10:36:14 +0100 > To: cygwin AT cygwin DOT com > >Max Bowsher wrote: >> Actually, pipe and kill might not be. Don't know. You'd have to look and >> find out. > >Well, the undefined references to pipe and kill were "solved" by linking >one of the "forbidden" libraries (-lcygwin, -lc, -lg...), so it seems there >are at least dummy implementations, or do I misinterpret this? > >As it looks like now, my only alternatives are: Linking one of those >"forbidden" libraries and getting a "multiple definition of `atexit'", >or not linking them and getting that bunch of undefined references. > >What can I do here? I've been sitting on this problem for a week now, and >I don't have any ideas what more to try. You are mixing the Cygwin and MinGW environments. This *will not work*. The thing you are trying to compile does not appear to have been ported to allow it to run on native Windows, and to run it on Cygwin would require a Cygwin-compiled gtk+, which is a whole new can of worms. You have 2 options, as far as I can see - give up, or devote lots of time to either porting GPA, or compiling a Cygwin gtk+ (and all its many dependencies.) 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/