X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <900C9A0E015B4755A763C4D4C0E60136@jeffPC> References: <900C9A0E015B4755A763C4D4C0E60136 AT jeffPC> Date: Sun, 9 May 2010 10:57:11 -0400 Message-ID: Subject: Re: Error building PowerPC Toolchain with Crosstool-NG in Cygwin From: Rahul Iyer To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I recently built PowerPC cross compilers on cygwin using crosstools, not crosstools-ng. I do have libncurses (10, 8 and 9) runtime libraries (not devel), and crosstools doesn't depend on ncurses. If your issue is still open I suggest you try crosstools. ./rahul On Sat, May 8, 2010 at 8:30 PM, Jeff Gilton wrote: > > 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. =A0It looks like it's trying to build in the Java support= so I disable Java and it gets farther. =A0Then it fails installing DUMA so= I disable that. =A0Then 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 vers= ion that will run in Windows. =A0I have tried to build it in Cygwin on Wind= ows 7, Windows 7 in XP compatibility mode, and Windows XP. =A0In all cases,= I have the latest version of Cygwin. > > I am not quite sure how to troubleshoot this. =A0Right 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. =A0I know it's not an error in CT_DoExecLog i= tself because that is used extensively and the build gets over 3/4 of the w= ay through. > > Any pointers on how to troubleshoot this will be greatly appreciated. > > Jeff Gilton > jgilton AT cinci DOT rr DOT com > > -- > Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html > FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ > Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html > Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple > -- 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