This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Release candidate: gcc-3.4.1-1
- From: "Gerrit P. Haase" <gerrit at familiehaase dot de>
- To: "Krzysztof Duleba" <krzysan at skrzynka dot pl>
- Cc: cygwin at cygwin dot com
- Date: Wed, 25 Aug 2004 20:28:31 +0200
- Subject: Re: [ANNOUNCEMENT] Release candidate: gcc-3.4.1-1
- Organization: Esse keine toten Tiere
- References: <05d701c48ace$cddbb2c0$0e00a8c0@duli2>
- Reply-to: "Gerrit P. Haase" <gerrit at familiehaase dot de>
Krzysztof schrieb:
> Gerrit P. Haase wrote:
>> > Is this true? I have 3.3.1 libraries in /lib and
>> > /lib/gcc-lib/i686-pc-cygwin/3.3.1, but 2.95 libraries only in
>> > /lib/gcc-lib/i686-pc-cygwin/2.95.3-10.
>>
>> There was no libjava with 2.x compilers. There was no libobjc with 2.x
>> compilers. What about libstdc++?
> As I said, 2.95 holds all its libraries, including libstdc++, in
> /lib/gcc-lib/i686-pc-cygwin/2.95.3-10.
Interesting, I would be interested why the previous maintainer switched
to unversioned runtime libs.
>> Hmmm, I don't like maintaining two versions of a package, if 3.4 is
>> stable it will be the one and only current version.
> I'm aware of it and that's why I'm asking. That would be the final release
> of 3.3, able to coexist with 3.4. Then you could happily forget about 3.3.
This is an option. I'll think about it.
> This would make no sense if 3.4 is binary compatible with 3.3. Are
> differences between 3.3 and 3.4 significant?
At least C++ has improved much and is not compatible (you cannot use one
libstdc++ for both versions.
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/