Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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, 14 Aug 2002 10:16:08 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: BUG: fork problems with libxml2
Message-ID:	<20020814141608.GD27499@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20020814122645 DOT 8526 DOT qmail AT web13706 DOT mail DOT yahoo DOT com> <17107620139 DOT 20020814161126 AT familiehaase DOT de>
Mime-Version:	1.0
In-Reply-To:	<17107620139.20020814161126@familiehaase.de>
User-Agent:	Mutt/1.3.23.1i

On Wed, Aug 14, 2002 at 04:11:26PM +0200, Gerrit P. Haase wrote:
>This is a problem with Cygwin fork().  You need to rebase the DLL's and
>all should work well then.  This needs Cygwin core development and
>meanwhile one needs to rebase the DLL's if there are problems with fork().
>Hint to the home of Cygwin-rebase:
>http://www.tishler.net/jason/software/rebase/

This is not a "cygwin problem" it is a "windows problem".  Actually, it
isn't even a "windows problem", since cygwin is trying to do something
that windows doesn't guarantee can be done.  It isn't clear to me that
there actually is a solution for cygwin.

However, if one was looking for an actual problem then people repeatedly
reporting the same "bug" would be a pretty obvious sociological problem.

cgf

--
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/

- Raw text -