We are supporting the compiler we shipped in Red Hat Linux 7.  If you
can add a bugzilla report with trimmed down test case of the code that
causes the error, we will do our best to get it fixed.

Follow the instructions at http://gcc.gnu.org/bugs.html but enter the
bug in bugzilla at http://bugzilla.redhat.com/bugzilla

We recommend that vendors depending on being portable to review the
Linux Development Platform Specification guidelines at
http://www.freestandards.org/ldps/1.0-beta/ldps-1.0-beta.html. (The
document is not final yet, so we can only recommend that you review
it.  When the final specification is released we will most likely
recommend that ISVs adhere to it when portability matters over
features).

   C++

   Because of the immaturity of C++ ABI (for name mangling and other
   such issues), we do not recommend depending on dynamic C++
   libraries provided with the system. It is possible, using existing
   Linux development tools, to development an application in C++ which
   links statically with libstdc++ and libgcc, or by providing these
   shared libraries with the application. These shared libraries
   should be located in an application-specific directory conforming
   to the /opt specification in FHS 2.1.

Cheers,

Matt

On Sat, Oct 07, 2000 at 09:12:26AM +0200, Mario Torre wrote:
> Hi,
> 
> Many problem are been posted about the version of gcc include in the
> RedHat Linux 7.0, these problem are about some difficulty of compiling
> C++ code.
> 
> Really, I don't know whene these errors occur, but it seems they make
> our code unportable.
> 
> I wish to know if there are some problem if I try to downgrade the
> gcc-2.69 with the latest and standard issue of the gnu c compiler
> (gcc-2.95).
> 
> As found on the gcc-bugs mailing list, they encourage any user to take,
> in case of doubt, the gcc-2.95.
> 
> I don't want to know about the reason of including the 2.96 with RedHat
> Linux 7.0, it's ok, but why there is no support for the official
> version?
> 
> A good strategy should be to give them two together... But that's my
> opinion, of course.
> 
> Thanks
> -----
> neugens
> 
> 
> 
> _______________________________________________
> Redhat-devel-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-devel-list



_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list

Reply via email to