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 02:54:00 -0000	[thread overview]
Message-ID: <3D2E65AC.1070509@ece.gatech.edu> (raw)
In-Reply-To: <20020712044319.GA10089@redhat.com>



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


<groan>

--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  5:14 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 [this message]
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=3D2E65AC.1070509@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).