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: Fri, 28 May 2004 23:35:31 +0200 From: Baurjan Ismagulov To: cygwin AT cygwin DOT com Subject: Re: dll version collision Message-ID: <20040528213531.GC1325@ata.cs.hun.edu.tr> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040527212657 DOT GC2617 AT ata DOT cs DOT hun DOT edu DOT tr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-IsSubscribed: yes Hello, Igor! On Thu, May 27, 2004 at 06:33:20PM -0400, Igor Pechtchanski wrote: > > * It isn't possible with the current cygwin. > It is possible, but non-trivial. Well, I've meant the binary DLL installed using setup. > One way to have Cygwin automatically modify the shared memory area name is > to compile it with debugging (by passing the --enable-debugging flag to > configure). Wow, it's even partly implemented! > The trick here is that once you have such a cygwin1.dll, > you'll have to spawn the process that uses it via Windows mechanisms, > rather than Cygwin's own fork. Thanks for the info! Do you know a good overview of exec, similar to that of fork, given in the user's guide? > I repeat: you really should know what you're doing before you attempt > this. I can't emphasize this enough. Are there any other implications that readily come to your mind? With kind regards, Baurjan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/