From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: serious C++ problem, and need for egcs release
13 Mar 1998 17:20:17 -0800
Message-ID: <199803140058.QAA11086.cygnus.cygwin32.developers@skaro.cygnus.com>
References: <9803132211 DOT AA00390 AT modi DOT xraylith DOT wisc DOT edu>
Content-Type: text
To: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Cc: cygwin32-developers AT cygnus DOT com

Mumit Khan wrote:
> 
> For some reason, Cygwin32 distributions seem to have very bad luck with
> C++!

Yeah, I know.  :-(  I made the decision to go ahead with releasing b19
on the basis that there would probably be a fixed egcs released for it
at some point relatively soon afterwards.

> will give you multiple definition errors (unless you use -O2). I know
> what the problem is and it's somewhat fixed in egcs (and really fixed
> in my distribution -- see my snapshot ftp area for patches).

Where is your snapshot area?

> We really need to get something usable out there, and I'm willing to put
> the egcs distribution together. Here's what I propose to distribute:

Great!

>   - egcs-1.0.2 (+ some patches): The test results are terrific.
> 
>   - binutils-980303: So far the most stable, and fixes some very serious
>     problems. With the latest fixes Ian has in there, it doesn't need any
>     patches. The only local patch is the NO_COPY handling in .data
>     section.
> 
> Now the question is of built-in pathnames. Should I build to "overwrite"
> the existing b19 one? Should it go outside (/usr/local)?

Probably best to overwrite the existing b19 C++-related stuff???  That
would be a prefix of /cygnus/b19 and exec-prefix of
/cygnus/b19/H-i386-cygwin32.

An area we're having trouble with is collect2 being broken.  Benjamin
Kosnik (bkoz) is planning on looking into it but hasn't had time yet.
If you have patches, please let him know?

-- 
Geoffrey Noer
noer AT cygnus DOT com