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

Hao Liu hliu at redhat.com
Tue Aug 26 19:05:12 PDT 2008


Wichmann, Mats D wrote:
> Wichmann, Mats D wrote:
>
> Sorry, I didn't see this was already answered in the flood of
> email in my inbox this morning (thanks, Denis!)
>
>
>   
>> 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:
>>
>> http://bugs.linuxbase.org/show_bug.cgi?id=2127
>>
>> _______________________________________________
>> lsb-discuss mailing list
>> lsb-discuss at lists.linux-foundation.org
>> https://lists.linux-foundation.org/mailman/listinfo/lsb-discuss
>>     
>
>   
Mats,
  That's OK, thank you for your reply.

All the best,
Hao Liu


More information about the lsb-discuss mailing list