Matt Wilson wrote:
> 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
>
Thank you, but that added another question.
Red Hat is an active part of the Linux standard, it is one of the major
distributors of it, and give to the open source a lot of great software
(see, above all, the rpm packaging system).
These are improvements.
But, as I can read by the Linux Development Platform Specification
guidelines, RedHat Linux 7.0 doesn't meet all the standards:
It is required the use of the gcc-2.95 maximum.
Really, I think it is not bad, don't misunderstand me, but, if you take a
look at what kind of errors the c++ compiler generate, you can find it is
immature for a development operating system.
Conservative reasons give to the RHL6.2 the egcs compiler, now RH ship an
experimental compiler with his major distribution.
And if I want to compile a program, and to use it with another distro?
That's not a new problem, I can remember of a library I was studing compiled
with SuSe Linux 6.0, that gave me a lot of problem with RedHat L.6.2,
Mandrake L. 7.0/7.1, and even with Slackware 7.0 and SuSe 6.2.
Note the last name, it gave me problem even with the SuSe 6.2.
But that library contained not very special issues.
The only thing we can do is to have the gcc included as basic compiler, but
to use some other compiler (gcc-2.95.2) as "portable compiler system".
I think it is important to say if this is possible, and if that's a good
idea.
A lot of people said RedHat Linux 7.0 it is not a good release, like most of
the RedHat x.0 it is not well tested, I think it is not true, as I have
followed any step of the development, I can relly say this time it is
different, and an upgrade to that new release is important, but I think it
is needed more info about that problem.
Thank you anyway,
neugens
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
