[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 --- Comment #8 from Eric Gallager --- (In reply to Eric Gallager from comment #7) > Patch: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591704.html Oh, this one is also relevant, too: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591734.html
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 Eric Gallager changed: What|Removed |Added URL||https://gcc.gnu.org/piperma ||il/gcc-patches/2022-March/5 ||91704.html --- Comment #7 from Eric Gallager --- Patch: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591704.html
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 --- Comment #6 from Tom Tromey --- (In reply to Eric Gallager from comment #4) > (In reply to Sergei Trofimovich from comment #3) > > (In reply to Sergei Trofimovich from comment #2) > > > Having explicit flags like --enable-systemtap / --disable-systemtap (glibc > > > has those) would fix the issue. > > > > Proposed upstream as: > > https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00578.html > > > > To clarify: it's not a complete fix for this bug. Only a way to disable > > support manually. > > I'll take this as confirmation. Also now that I've seen the actual code in > this patch, I can say that my previous comment (comment #1) no longer > applies, since the script is just doing `test -f` instead of > AC_CHECK_HEADERS. IIRC that's because it has to check target headers, but AC_CHECK_HEADERS checks host headers. Maybe there's some other way to do it, I don't know. It's fine to really check the header, but I would say the scenario in comment #2 has to fall under "don't do this". That said, a --enable flag or whatever also seems fine to me.
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 Eric Gallager changed: What|Removed |Added CC||tromey at gcc dot gnu.org --- Comment #5 from Eric Gallager --- svn blame says Tom Tromey added the original check for ; cc-ing him
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 Eric Gallager changed: What|Removed |Added Keywords||build, patch Status|UNCONFIRMED |NEW Last reconfirmed||2018-05-12 Ever confirmed|0 |1 --- Comment #4 from Eric Gallager --- (In reply to Sergei Trofimovich from comment #3) > (In reply to Sergei Trofimovich from comment #2) > > Having explicit flags like --enable-systemtap / --disable-systemtap (glibc > > has those) would fix the issue. > > Proposed upstream as: > https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00578.html > > To clarify: it's not a complete fix for this bug. Only a way to disable > support manually. I'll take this as confirmation. Also now that I've seen the actual code in this patch, I can say that my previous comment (comment #1) no longer applies, since the script is just doing `test -f` instead of AC_CHECK_HEADERS.
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 --- Comment #3 from Sergei Trofimovich --- (In reply to Sergei Trofimovich from comment #2) > Having explicit flags like --enable-systemtap / --disable-systemtap (glibc > has those) would fix the issue. Proposed upstream as: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00578.html To clarify: it's not a complete fix for this bug. Only a way to disable support manually.
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 Sergei Trofimovich changed: What|Removed |Added CC||slyfox at inbox dot ru --- Comment #2 from Sergei Trofimovich --- In a related bug I'd like to have explicit flag to disable systemtap. In https://bugs.gentoo.org/654748 user was compiling gcc and uninstalling systemtap in parallel. This caused gcc to detect systemtap presence at configure time and fail a build when std.h was used. Uninstalling happened because gcc has no explicit dependency on systemtap. Having explicit flags like --enable-systemtap / --disable-systemtap (glibc has those) would fix the issue. Thanks!
[Bug other/61257] configure should check if sys/sdt.h is usable, not just checking the existance of the header
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment #1 from Eric Gallager --- Maybe once autoconf 2.70 is released, this bug could be fixed just by updating to it, since autoconf 2.70 will change all tests for header existence to tests for header usability.
