[Bug 1011] New: appchk new fails on IA64

[email protected]
Newsgroups gmane.linux.lsb.test-suite
Message-ID <[email protected]>
After fixing bug 997 - setting the correct flags on .sbss for ia64 - a couple of
situations emerged where appchk is looking for the new value and doesn't see it!
These cases all occurred where the app includes an app-supplied shared library.

In Apache, OpenJade from appbat:
Section .sbss: sh_flags is wrong. expecting 10000003, got 1

In Tcl from appbat:
Section .rodata: sh_flags is wrong. expecting 2, got 32
Section .sbss: sh_flags is wrong. expecting 10000003, got 3

(note also the .rodata complaint)

Each of these includes non-LSB shared libs (i.e. app-provided):
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-apache/opt/lsb/appbat/lib/libapr-0.so.0
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-apache/opt/lsb/appbat/lib/libaprutil-0.so.0
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-apache/opt/lsb/appbat/lib/libexpat.so.0

Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-openjade/opt/lsb/appbat/lib/libostyle.so.0
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-openjade/opt/lsb/appbat/lib/libospgrove.so.0
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-openjade/opt/lsb/appbat/lib/libogrove.so.0
Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-openjade/opt/lsb/appbat/lib/libosp.so.4

Adding symbols for library
/home/heffler/LSB/appbat/pkgroot/lsb-tcl/opt/lsb/appbat/lib/libtcl8.4.so

The appbat Expect includes the same libtcl library but does not take this error
message.

Also note appbat Python uses lots of shared libs, but they are dlopen'd so they
are not checked by lsbappchk (not in DT_NEEDED)   
 
--    
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email   
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.