--- Jakub Jelinek <jakub(a)redhat.com> wrote: > On Thu, Jul 31, 2003
at 04:45:43PM +0200, Milan Kerslager wrote:
> On Thu, Jul 31, 2003 at 05:10:45AM -0400, Jakub Jelinek wrote:
> > On Thu, Jul 31, 2003 at 10:01:20AM +0100, Mike Martin wrote:
> > > previously, when RH has included a new compiler, compat
> > > been included for previous version
> > But gcc 3.2.x is compatible with gcc 3.3.x (there are some
> > but I believe gcc 3.2.x would simply ICE on them rather than
> > ABI incompatible code with gcc 3.3.x).
> So there is the last question: Do we need compat-libstdc++ from
Depends if you need that compatibility or not.
compat-libstdc++ in Cambridge provides 2.96-RH, egcs 1.1.2 and some
libstdc++'s. If you have something still compiled against them, you
them, otherwise you don't.
Ok lets see if I can persuade you
Imagine this scenario
You are trying to compile a program that uses/links against c and c++
code (eg:gstreamer, abiword)
The program fails to compile with an error message suggesting strict
checking is making the build fail.
So to confirm you would like to test compiling with gcc32 and g++32
If it builds you can then confirm that gcc3.3 strictness is the
Therefore you can write a more considered bug report so the problem
gets fixed in the package
Rhl-beta-list mailing list
Yahoo! Plus - For a better Internet experience