X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.7 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=1.1 cv=Ebn0m7KaSvUJV60GCOzUqyhjUj7QmnsyUUVbVvk8w6o= c=1 sm=0 a=nX3YnGcTQbAA:10 a=8nJEP1OIZ-IA:10 a=fvawE18eGI/ltQWmdMGOJg==:17 a=ayC55rCoAAAA:8 a=sZSQ9Q9TT7WrOmgsAfwA:9 a=wdm9vZ-bvs9fcRh1i2EG3NW7OlsA:4 a=wPNLvfGTeEIA:10 a=fvawE18eGI/ltQWmdMGOJg==:117
Message-ID:	<900C9A0E015B4755A763C4D4C0E60136@jeffPC>
From:	"Jeff Gilton" <jgilton AT cinci DOT rr DOT com>
To:	<yann DOT morin DOT 1998 AT anciens DOT enib DOT fr>
Cc:	<crossgcc AT sourceware DOT org>, <cygwin AT cygwin DOT com>
Subject:	Error building PowerPC Toolchain with Crosstool-NG in Cygwin
Date:	Sat, 8 May 2010 20:30:19 -0400
MIME-Version:	1.0
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

I am trying to build a PowerPC toolchain with Crosstool-NG version 1.7.0. 
It gets most of the way through then fails installing the final C compiler 
in CT_DoExecLog.  It looks like it's trying to build in the Java support so 
I disable Java and it gets farther.  Then it fails installing DUMA so I 
disable that.  Then it fails building ncurses but I could find no way to 
disable that.

I was able to successfully build the toolchain on Linux but I need a version 
that will run in Windows.  I have tried to build it in Cygwin on Windows 7, 
Windows 7 in XP compatibility mode, and Windows XP.  In all cases, I have 
the latest version of Cygwin.

I am not quite sure how to troubleshoot this.  Right now, I've modified 
crosstool-NG-sh to run bash in verbose mode to see if it can tell me where 
the build is really failing.  I know it's not an error in CT_DoExecLog 
itself because that is used extensively and the build gets over 3/4 of the 
way through.

Any pointers on how to troubleshoot this will be greatly appreciated.

Jeff Gilton
jgilton AT cinci DOT rr DOT com 


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