X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
Message-ID:	<4F6240ED.5030101@cs.utoronto.ca>
Date:	Thu, 15 Mar 2012 15:20:13 -0400
From:	Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version:	1.0
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Fork errors during toolchain build
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Hi all,

I'm trying to build a crosstool chain under cygwin and I keep getting 
blocked by fork errors -- in spite of having rebased just before 
starting. Oddly, the errors come from scripts, not invocations of 
just-built-gcc (which used to be the killer). Unfortunately, this means 
there's no obvious culprit to target, because presumably the dlls bash, 
sed, etc. use were rebased before the build ever started.

Is there some way I can diagnose more precisely what binaries/dlls are 
responsible so I can rebase the right things? I can't rule out the 
existence of custom dlls, but I did rebase everything newly-built that I 
could find.

Thanks!
Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -