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 09:22:00 -0000	[thread overview]
Message-ID: <3D2EF62E.1040209@ece.gatech.edu> (raw)
In-Reply-To: <20020712052250.GB30885@redhat.com>



Christopher Faylor wrote:

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


Well, I guess "normal" wasn't the correct term.  I'm using Danny's 
gcc-2.95.3 -src package from mingw.org (seemed appropriate since I was 
building a mingw-target compiler).

I'm unsure how large the differences are between your version and 
Danny's (of 2.95.3).  I guess I'll find out...


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


As in, "a PITA to maintain".  Hopefully, gcc2 will be a "release and 
forget" package.


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



<Argh!> Sounds very frustrating.  Thanks for all your hard work -- and 
take care of your hands.

--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 15:30 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
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 [this message]
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=3D2EF62E.1040209@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).