From: "thaines.astro at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/31241] New: Python/Java probes do not build out-of-source
Date: Fri, 12 Jan 2024 17:03:57 +0000 [thread overview]
Message-ID: <bug-31241-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31241
Bug ID: 31241
Summary: Python/Java probes do not build out-of-source
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uprobes
Assignee: systemtap at sourceware dot org
Reporter: thaines.astro at gmail dot com
Target Milestone: ---
Created attachment 15298
--> https://sourceware.org/bugzilla/attachment.cgi?id=15298&action=edit
configure log
java/SDTHelper.c and python/HelperSDT/_HelperSDT.c require '<sys/sdt.h>', but
it is not copied into the build directory for out-of-source builds.
running build
running build_py
running build_ext
building 'HelperSDT._HelperSDT' extension
x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2
-Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv
-O2 -I../../python/../includes
-I/path/to/systemtap/build/python/../includes/sys -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c HelperSDT/_HelperSDT.c
-o
/path/to/systemtap/build/python/py3build/temp.linux-x86_64-3.10/HelperSDT/_HelperSDT.o
HelperSDT/_HelperSDT.c:10:10: fatal error: sys/sdt.h: No such file or directory
10 | #include <sys/sdt.h>
| ^~~~~~~~~~~
python/Makefile.am seems to want to allow this case:
AM_CPPFLAGS += -I$(abs_builddir)/../includes/sys
However, that doesn't work for two reasons:
1. The headers are included as <sys/sdt.h>, so the trailing 'sys' above
prevents finding the header in build/includes.
2. Fixing (1) now finds systemtap/includes/sdt.h, but can't find sdt-config.h
which lives in build/includes.
There is likely a simple solution here, but my autotools-foo is rusty. Any
thoughts are appreciated!
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-01-12 17:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31241-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).