[EMAIL PROTECTED] said:
> Furthermore, RH7 apps will not be compatible with ohter Linuxes, so
> if you build your app on RH7 and ship it to a user who's not using
> RH7, the app will act funny, since the target system ABI is not
> compatible.
I'm a bit doubtful that gcc will cause this kind of
[EMAIL PROTECTED] said:
> This only applies for C++, where there is no standard ABI and haven't
> been - _for C, it is binary compatible_.
>
To me, "binary compatibility" has always meant something a little different.
On OS/2, DOS, Windows* one has a choice of C and C++ compilers. Shared
l
plies for C++, where there is no standard ABI and haven't
been - _for C, it is binary compatible_.
> > One more question, the gcc-2.95.3 is the official release that would
> > probabily be the gcc-3.0, so the standards will meet there again.
2.95.3 just fixes some of the (_many_)
If you want to compile applications on RH7.0, use their gcc-2.96 compiler.
RH's 2.96 has a different ABI (application binary interface) and code-generation
style than basically any other Linux system out there. They used that compiler
to compile all their libraries.
if you build gcc.2.95
ort, ...)
> The binary code will be compatible or there are the same differences as in
> the past with gcc-2.95.2 and gcc-2.96?
2.95.3 == 2.95.2 + minor fixes.
> One more question, the gcc-2.95.3 is the official release that would
> probabily be the gcc-3.0, so the standards will meet there
Hi, today I have received the annunce of the gcc-2.95.3
What are the differences between the gcc-2.96 (rh) and this gnu gcc-2.95?
The binary code will be compatible or there are the same differences as in
the past with gcc-2.95.2 and gcc-2.96?
I had no problems with the new gcc-96, after the
