From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30506 invoked by alias); 8 Feb 2006 23:23:54 -0000 Received: (qmail 30497 invoked by uid 22791); 8 Feb 2006 23:23:54 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 08 Feb 2006 23:23:52 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1F6yf5-0002Or-Oy; Wed, 08 Feb 2006 18:23:47 -0500 Date: Wed, 08 Feb 2006 23:23:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: bob@brasko.net, gdb-patches@sourceware.org Subject: Re: RFA: Support Windows extended error numbers in safe_strerror Message-ID: <20060208232347.GB9008@nevyn.them.org> Mail-Followup-To: Mark Kettenis , bob@brasko.net, gdb-patches@sourceware.org References: <20060203215455.GA3501@nevyn.them.org> <20060206173550.GB22947@nevyn.them.org> <200602062254.k16MsagK009925@elgar.sibelius.xs4all.nl> <20060206225829.GA31895@nevyn.them.org> <20060208000855.GA5040@nevyn.them.org> <200602082107.k18L7xRh013417@elgar.sibelius.xs4all.nl> <20060208211349.GH3975@brasko.net> <200602082316.k18NG28Q031774@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602082316.k18NG28Q031774@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00194.txt.bz2 On Thu, Feb 09, 2006 at 12:16:02AM +0100, Mark Kettenis wrote: > I always understood having two different versions of a DLL with the > same name as being the "DLL hell" problem. Am I wrong? I can't > believe that in the last 10 years that people have been talking about > this problem, MicroSoft didn't come up with a solution for it. And > even if they didn't, the solution is simple: just ship the Cygwin > DLL's under a different name. Or just link the Cygwin code > statically. Or is that impossible on Windows? My understanding is that this is incompatible with the design of Cygwin, and e.g. the mechanisms it uses to manage "emulated" inter-process resources that don't map obviously onto Windows. Like character devices and TTYs, to give some relevant examples. -- Daniel Jacobowitz CodeSourcery