X-Spam-Check-By: sourceware.org Message-ID: <4672C1F4.6010306@users.sourceforge.net> Date: Fri, 15 Jun 2007 11:44:36 -0500 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Some notes on building gcc-4.3.0 References: <466F9B52 DOT 1000709 AT cwilson DOT fastmail DOT fm> In-Reply-To: <466F9B52.1000709@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charles Wilson wrote: > I was testing Danny Smith's latest DWARF-2 patch, and building gcc from > the current (rather unsettled) trunk was a bit tricky. So, I thought > I'd post my experiences, which ultimately resulted in a fully > bootstrapped native cygwin compiler, with c,c++,objc,fortran,java > frontends. Thanks for the update; I was going to ask about the progress on this. > First, I had to massage the tree in the following ways (and I was using > revision 125636): Out of curiosity, have you done this with cygport yet? > This made it all the way thru the three-stage bootstrap, and built most > of the libraries. However, the build failed in libjava, due to stack > overflow in jc1.exe. After manually relinking cc1.exe and jc1.exe with > 100MB of stack (-Wl,--stack,102400000) as recommended here: > http://gcc.gnu.org/ml/gcc/2007-06/msg00151.html Interesting. I wonder if this would help with linking libsmokekde and libkdejava, both of which fail during linking for the same reason. Perhaps the other compilers should also be built with this flag for the same reason (and binutils' ld as well)? - From your notes, I gather that all libs are being built shared. If so, that's very good news, and I look forward to seeing this become readily available. To that end, a few questions: 1) What progress is being made to get these patches included upstream? 2) How long before gcc-4.3 will be stabilized enough to be generally usable? 3) Could you and/or others working on this keep this list updated on further progress? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGcsH0piWmPGlmQSMRCNgJAJ9iSQYuES950VqWQOOOOeeJuFrsOwCfQn8S 6a+fDRJH1I6uCcx+EoWaa9I= =Uz0v -----END PGP SIGNATURE----- -- 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/