C++ ABI in LSB 2.0 is broken [LWN.net]

C++ ABI in LSB 2.0 is broken

Posted Sep 14, 2004 20:20 UTC (Tue) by subhasroy (guest, #325)
Parent article: The Open Group & FSG announce LSB 2.0 certification

A knowledgeable person Joe Buck (who is involved with GNU C++ project) said the following about the C++ ABI support in LSB 2.0:

.. the promise of C++ support in the LSB is broken and the document is self-contradictory, in that it simultaneously specifies an ABI and requires a shared library that does not correctly implement that ABI, and it therefore forces LSB-compliant apps to use an obsolete version of the GNU C++ compiler, although it does not clearly state this fact.

ref:

http://linuxtoday.com/news_story.php3?ltsn=2004-09-14-018...

There was plenty of unhappiness expressed on the same issue earlier. I am puzzled that still the final 2.0 spec has not addressed the concern.

(Log in to post comments)

C++ ABI in LSB 2.0 is broken

Posted Sep 14, 2004 22:12 UTC (Tue) by nix (subscriber, #2304) [Link]

It's even worse than Joe said. Presently, for LSB conformance, one must use a simultaneously obsolete and unreleased version of G++: specifically, the 3.3 branch CVS HEAD.

This cannot be good.

C++ ABI in LSB 2.0 is broken

Posted Sep 14, 2004 23:10 UTC (Tue) by JoeBuck (subscriber, #2330) [Link]

GCC 3.3.5 will be released soon. Even so, what bothers me more than anything is that GCC 3.4 is the first release with a C++ parser that is not an unmaintainable kludge (the result being that hundreds of long-standing C++ parser bugs were fixed in 3.4), and the LSB committee has seen fit to require that 3.3 will have to continue to live indefinitely.

And there's also the disaster that GCC 3.2-based distros are still in wide use, they also have a libstdc++.so.5, and they are incompatible with GCC 3.3.