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

Karel Srot ksrot at redhat.com
Fri Apr 26 11:58:26 UTC 2013


I have notices some note regarding libchk in recent LSB conference call
minutes (I hope it is not something for LF eyes only) and I have a
question on this topic. 

Currently we are facing several failures in Library check on ppc64
similar to
Actually, there are not new, there are present even in RHEL6.0 with LSB
4.0. There is also a lot of warning on all architectures. The only
difference is that the Warning contains following note in the log:
  """ But this case looks like re-implementation of virtual function in
      derived class, which is OK in most cases. """

I would like to know what is the current status of libchk (on ppc64),
whether I should take these failures seriously or not.
Also, I do not fully understand exactly the analysis performed by
libchk. Would it be possible to describe the process with manual steps
e.g. using objdump or readelf? This would help me a lot with the

Thank you in advance.


Karel Srot
Quality Engineer, QE BaseOS Security team

Email: ksrot at redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic

More information about the lsb-discuss mailing list