public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: cygwin@cygwin.com
Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
Date: Fri, 12 Jul 2002 00:31:00 -0000	[thread overview]
Message-ID: <3D2E5C1B.9050604@ece.gatech.edu> (raw)
In-Reply-To: <20020712040949.GB2057@redhat.com>

Christopher Faylor wrote:

> 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.


Hmm...


> 
> I don't think that g77 -mno-cygwin ever worked before, AFAICT.  


Perhaps not -- I was just being thorough.

>  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.


Cool.

 
> gcc2 is supposed to be going away someday (soon). 


As long as there are (supported) C++ libraries that use the 2.95.3 ABI, 
we'll need gcc2.  E.g.  libncurses6++, and the others that were 
mentioned onlist, unless gcc-3.1.1 goes gold before they do.

> I am just trying to
> repackage it so that people aren't left with problems in the short term.


Right, good, good...


> 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. 


Absolutely.

> I'm not
> going to complicate the process by adding extra packages.


Oh, okay -- if you're going to add the mingw libs directly into gcc2, 
that'll work.  And, since gcc2 will be effectively frozen, hopefully 
maintainance will drop to practically nil, so might as well anticipate 
things now...

 
> 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 understand.

>  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.


Right.

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


Nifty keen.

 
'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.


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...

--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/

  reply	other threads:[~2002-07-12  4:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11  2:19 Christopher Faylor
2002-07-11  3:47 ` Charles Wilson
2002-07-11  3:49   ` Charles Wilson
2002-07-11  6:47     ` Nicholas Wourms
2002-07-11  8:26       ` Charles Wilson
2002-07-11 20:26     ` Christopher Faylor
2002-07-11 20:50       ` Christopher Faylor
2002-07-11 10:19   ` Christopher Faylor
2002-07-11 11:56     ` Charles Wilson
2002-07-11 21:09       ` Christopher Faylor
2002-07-11 21:33         ` Unscrible--liangalei@CS.SJTU.EDU.CN liangalei
2002-07-11 23:59         ` Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Charles Wilson
2002-07-12  0:27           ` Christopher Faylor
2002-07-12  0:31             ` Charles Wilson [this message]
2002-07-12  1:32               ` Christopher Faylor
2002-07-12  2:54                 ` Charles Wilson
2002-07-12  4:40                   ` Christopher Faylor
2002-07-12  9:22                     ` Charles Wilson
2002-07-12 18:46                       ` Christopher Faylor
2002-07-12  7:27               ` Nicholas Wourms
2002-07-15  0:55   ` Charles Wilson
2002-07-15  1:09     ` Christopher Faylor
2002-07-15  8:02       ` Nicholas Wourms
2002-07-15 11:56         ` Charles Wilson
2002-07-15 12:36           ` Nicholas Wourms
2002-07-11  7:19 ` Nicholas Wourms
2002-07-11  9:05   ` Christopher Faylor
2002-07-11 14:26     ` Nicholas Wourms
2002-07-11  8:49 ` Pavel Tsekov
2002-07-12  2:38   ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D2E5C1B.9050604@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).