[lsb-discuss] lsb-libchk of LSB3.2 failed

Wichmann, Mats D mats.d.wichmann at intel.com
Tue Aug 26 05:32:34 PDT 2008

Hao Liu wrote:
> Hi, guys,
>   i'm running lsb-libchk-3.2.2-1, there're 14 failed all about
> libQtSvg.so.4 :
>     libQtSvg.so.4 86 FAIL
>     libQtSvg.so.4 87 FAIL
>     libQtSvg.so.4 88 FAIL
>     libQtSvg.so.4 90 FAIL
>     libQtSvg.so.4 91 FAIL
>     libQtSvg.so.4 92 FAIL
>     libQtSvg.so.4 93 FAIL
>     libQtSvg.so.4 96 FAIL
>     libQtSvg.so.4 97 FAIL
>     libQtSvg.so.4 98 FAIL
>     libQtSvg.so.4 100 FAIL
>     libQtSvg.so.4 101 FAIL
>     libQtSvg.so.4 102 FAIL
>     libQtSvg.so.4 103 FAIL
> I really don't know what's going wrong here, becos I find I can't find
> the test cases from the source:
> src/lsb-libchk-3.2.1/tests/misc/libchk/libQtSvg_so_4.c

General answer:

You're looking at the testcases, but it's not going to
correlate easily, since it's a long list with #ifdefs.
You need to look at the test journal, just search for
the tag FAIL, and you should see what the names of the
routines it's looking for are.  libchk does no testing of
behavior at all, so failures mean missing symbols in your
library (or possible mis-versioned symbols, but not in
the case of the Qt4 libraries, which are not symbol versioned).

Specific answer:

We know about this problem, a fix exists but has not been
pushed to the 3.2 branches yet.  See:


More information about the lsb-discuss mailing list