Hi, [ Adding reporter of #726248 to CC and quoting the bug report fully for him. ]
Matthias Klose <d...@debian.org> writes: > 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> thanks for the report. systemtap-sdt-dev was made arch:all in response to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726248 I'm not sure if I'm getting the whole picture here, what's the cause of the build failure? I could take a look at the issue on a porterbox, is there something smaller than gcc that FTBFS due to this issue? gcc is bit heavy to debug :( -Timo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
