[lsb-discuss] what is the current libchk status in LSB 4.0 and 4.1?

Benjamin De Kosnik bkoz at redhat.com
Tue May 21 17:00:48 UTC 2013

> > It's a general accounting error with abstract virtuals in
> > instantiated templates in libchk. FWICT, This has been an issue for
> > years on ppc64.

The bugs. LSB 3579, 3580.

> > There's an additional issue in that one of these libstdc++ exports
> > is not necessary (but harmless): the ctype<char> vtable explicitly
> > elides the abstract base, but it is explicitly instantiated and
> > exported just the same. Because it's never used, it doesn't really
> > matter what the values are.

An additional issue, LSB 3602 only.

> Just so I understand, it's your belief that ctype<char>'s abstract
> base should explicitly not be a part of the LSB? 

No, it has to be present as it was exported from the beginning, and we
cannot just remove symbols, it breaks ABI.

Since it cannot be used, its value doesn't matter. Thus, libchk
shouldn't care. 


More information about the lsb-discuss mailing list