Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 12 Jul 2002 01:22:50 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Message-ID: <20020712052250.GB30885@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020711044304 DOT GA3292 AT redhat DOT com> <3D2D3205 DOT 7080606 AT ece DOT gatech DOT edu> <20020711162955 DOT GA11047 AT redhat DOT com> <3D2DBE07 DOT 3040909 AT ece DOT gatech DOT edu> <20020712000601 DOT GA11148 AT redhat DOT com> <3D2E51ED DOT 3080902 AT ece DOT gatech DOT edu> <20020712040949 DOT GB2057 AT redhat DOT com> <3D2E5C1B DOT 9050604 AT ece DOT gatech DOT edu> <20020712044319 DOT GA10089 AT redhat DOT com> <3D2E65AC DOT 1070509 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D2E65AC.1070509@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Fri, Jul 12, 2002 at 01:14:20AM -0400, Charles Wilson wrote: >>It is in the last two lines of the specs file: >> >>#define LIBSTDCXX "-lstdc++-2" >>#define FORTRAN_LIBRARY "-lg2c-2" > > >I'll look for it -- it's not in my "normal" sources, so I guess normal >sources use a default definition from somewhere else. I'll download >your gcc2-src package and use that... The gcc-2.95.3 that I distribute has a lot of gcc/mingw changes. Many of them come from Mumit. So, if you grab "my" package you get something that is different from the sources at gcc.gnu.org. >>The files themselves get munged by mknetrel's extra/gcc2 script. > >Ah. But if you munge the filenames at install time, then don't stage2 >and stage3 break? I copy around stuff by hand for the first stage (building the cross compiler). I don't build a native compiler first, so there are only two stages. And, yes, copying stuff around by hand is a real pain... >>(Who's off for the 4000th rebuild of these packages...) > > > I'm on 4001 now. Forgot to merge with the current gcc branch. Looked like an possible code gen bug got fixed. Thank god for ccache, though. I'd still be scratching my head about the best way to deal with -mno-cygwin if it wasn't for that. It's really amazing. Oops. Forgot to regen stage one for this go-around. That would screw up the specs file. Time for build 4002 and 4003. 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/