flame@yamato systemtap % checkrdeps systemtap net-dns/avahi (/usr/lib64/libavahi-client.so.3) net-dns/avahi (/usr/lib64/libavahi-common.so.3) dev-libs/nss (/usr/lib64/libssl3.so) dev-libs/nss (/usr/lib64/libsmime3.so) dev-libs/nss (/usr/lib64/libnss3.so) dev-libs/elfutils (/usr/lib64/libdw.so.1) dev-libs/elfutils (/usr/lib64/libelf.so.1) dev-libs/nspr (/usr/lib64/libnspr4.so) sys-libs/glibc (/lib64/libpthread.so.0) sys-libs/glibc (/lib64/libm.so.6) sys-libs/glibc (/lib64/libc.so.6) I found this one while fixing the buildsystem to use pkg-config to discover those...
I sent upstream a patch to allow disabling NSS and Avahi, and to check for them with pkg-config so that it can be cross-compiled. As it happens, systemtap 1.6 does _not_ build without NSS, as it lacks some conditionals: In file included from csclient.cxx:12: cscommon.h:7:17: error: ssl.h: No such file or directory In file included from csclient.cxx:12: cscommon.h:48: error: ISO C++ forbids declaration of ‘CERTCertificate’ with no type cscommon.h:48: error: expected ‘,’ or ‘...’ before ‘*’ token make[2]: *** [stap-csclient.o] Error 1 make[2]: Leaving directory `/build/arm-generic/tmp/portage/dev-util/systemtap-1.6/work/systemtap-1.6'
Okay I was able to get two patches upstream, one to fix the discovery of the two (so that it uses pkg-config) and another to add --without options that allows us to disable code for both. But the collapse of the two can't be applied over 1.6, I have a port over 1.6, so I could commit this with an avahi USE flag right away, if you wish.
Created attachment 285643 [details] systemtap-1.7_pre20110903.ebuild This is an ebuild for the latest snapshot, that includes my patches and the disabled-NSS fixes, which means it can be used without applying futher patches. I also bumped the ebuild to EAPI=4 as it shortens it a bit.
Should be fixed in 2.0 I think
