Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 12 Jul 2002 00:09:49 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
Message-ID: <20020712040949.GB2057@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D2E51ED.3080902@ece.gatech.edu>
User-Agent: Mutt/1.3.23.1i

On Thu, Jul 11, 2002 at 11:50:05PM -0400, Charles Wilson wrote:
>g++ -mno-cygwin works

Actually, this fails for me, for some reason.

>>Sorry.  I was slow.  It took me about twenty seconds.
>>
>>You can disregard this email.
>
>I gather you figured out what was "wrong" with g77-2 in gcc2-2.95.3-8 ?

Yes, the lack of libg2c-2.a.  :-(  The 3.1.1 version was always being
picked up.  So if you tried this before installing 3.1.1, it worked.

I tried reinstalling gcc 2.95.3-5 to see if that worked, and, of course,
it did.  Once I installed that, gcc-2 started working, too.  Doh.  So,
I've got a new version of gcc2 coming.

I don't think that g77 -mno-cygwin ever worked before, AFAICT.  I guess
it should.  So, I give up.  The next version of gcc2 will have mingw
libraries for libg2c-2.a and libstdc++-2.a.

>P.S. Now, my tests are very very simple.  Consider them "basic" 
>functionality tests.  We still need more "real world" testing before 
>these are ready to go, IMO.
>
>Also, I'm thinking that the files in
>  /usr/include/g++-3/ (including _G_config.h)
>should go into a
>  gcc2-mingw-2.95_YYYYMMDD-X
>package (perhaps along with

gcc2 is supposed to be going away someday (soon).  I am just trying to
repackage it so that people aren't left with problems in the short term.
It's a royal pain to support this.  Once gcc2 seems as stable as
2.95.3-5 used to be, that will be it for any further releases.  I'm not
going to complicate the process by adding extra packages.

I know that Danny will be coming out with new 3.1 versions of gcc for
mingw and that they will not be tied in any way to my gcc releases, so I
thought it prudent to split the mingw stuff out so that I wouldn't have
to respin the whole, huge gcc 3.1.1 package.  I don't have to do that
for 2.95.3.  It's not going anywhere.  I doubt that Danny will be
making future releases or I'll be building mingw gcc's myself.

>usr/lib/mingw/libgcc.a

The 2.95.3-* version of libgcc.a is mingw compatible.  I went to some
pains to ensure that.

>usr/lib/mingw/libobjc.a
>usr/lib/mingw/libstdc++.a from mingw's gcc, appropriately '-2' renamed)
>
>Hey, wait a minute -- maybe that's why g77-2 is failing?  It's linking 
>against libg2c.a from 3.1?  Yep, seems so!

Yep, you got it.

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/