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 Message-ID: <3D2E65AC.1070509@ece.gatech.edu> Date: Fri, 12 Jul 2002 01:14:20 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 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> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > On Fri, Jul 12, 2002 at 12:33:31AM -0400, Charles Wilson wrote: > >>'Course, for my cygwin-host, mingw-target cross compiler, I'll need to >>respin >>it so that it coexists with the official gcc and gcc2 and gcc-mingw >>packages...sigh. >> > > Do you need this anymore, though? Perhaps not. It was really just an experiment: everybody including me has been claiming that "just build a real cross-compiler; that's 'the right way to do it'" so I gave it a shot. It wasn't as easy as everyone thought. Lots of weirdness (mostly in directory layout) to make it coexist peacefully with the mingw bits of cygwin. > You could get by with this, couldn't > you: > > i686-pc-mingw32-gcc is: > #!/bin/sh > gcc -mno-cygwin $(@+"$@"} Probably. > > Or, should I not be coopting the i686-pc-mingw32 target directory? > Maybe it really should be something like i686-pc-mingw32-cygwin. Bleah. No, I think you made the right choice. Besides, my cross compiler goes into /opt/mingw/* -- so no conflict there. Also, if one were to install mingw itself, it goes into /mingw. >>Say, where do you change gcc(2.95.3) so that g++-2 links against >>libstdc++-2.a instead of libstdc++.a? (Ditto g77). It doesn't seem to >>be in the specs file, so I dunno WHERE that is done... >> > > 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 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? > Btw, I moved that libstdc++.a.whatever file out of /usr/lib for the next > release. Although, actually, if I had just moved it into the > /usr/i686-pc-cygwin/lib directory, I might not have had to add the -2 > part. Argh. Not going to change it now... Agreed -- I actually LIKE the -2 distinction. > > cgf > (Who's off for the 4000th rebuild of these packages...) --Chuck -- 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/