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 Date: Wed, 20 Nov 2002 10:36:14 +0100 From: Markus Gerwinski To: cygwin AT cygwin DOT com Subject: Re: Conflict between libcygwin.a and GCC core libraries Message-ID: <20021120093614.GA1698@leia.local> References: <20021119160845 DOT GC4923 AT leia DOT local> <005801c28fe7$99b309a0$78d96f83 AT pomello> <20021119163413 DOT GA5773 AT leia DOT local> <00f201c28feb$863e1fa0$78d96f83 AT pomello> <20021119170642 DOT GA6139 AT leia DOT local> <013301c28ff1$0963a210$78d96f83 AT pomello> <20021119175023 DOT GA6789 AT leia DOT local> <005c01c29000$8ecdd8d0$78d96f83 AT pomello> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005c01c29000$8ecdd8d0$78d96f83@pomello> User-Agent: Mutt/1.3.27i 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. Markus -- 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/