Package: systemtap Version: 2.3-2 Severity: serious Tags: sid jessie The sys/sdt.h header file is shipped in an architecture independent package, and installed into /usr/include where it is found on the include path for every architecture. Seen that the mere inclusion of this header causes build failures on some architectures. Reported in
https://gcc.gnu.org/PR61231 and before in https://gcc.gnu.org/ml/gcc-patches/2012-12/msg01122.html This just seems to be the visible fall-out, what about issues on architectures not supported by systemtap? In bug #423934 you mention that systemtap should be only available on architectures where it is supported. The systemtap-sdt-dev package violates this assurance. So the correct solution for this seems to be an architecture dependent systemtap-sdt-dev package shipping the header file in /usr/include/<multiarch> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
