This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/25266] New: Log configure command output when compiling modules
- From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 10 Dec 2019 06:12:15 +0000
- Subject: [Bug runtime/25266] New: Log configure command output when compiling modules
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=25266
Bug ID: 25266
Summary: Log configure command output when compiling modules
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: craig.ringer at 2ndquadrant dot com
Target Milestone: ---
The runtime configure commands' output is not logged anywhere. From the
generated Makefile for module builds:
~~~
@if $(CHECK_BUILD)
$(SYSTEMTAP_RUNTIME)/linux/autoconf-linux-sched_headers.c > /dev/null 2>&1;
then echo "#define STAPCONF_LINUX_SCHED_HEADERS 1"; fi >> $@
~~~
all output is sent to /dev/null .
This made diagnosis rather harder in #25265
I suggest redirection of stdout to stderr instead, and bracketing it with an
echo. Like
~~~
@echo Runtime configure test linux/autoconf-linux-sched_headers.c for
STAPCONF_LINUX_SCHED_HEADERS:
@if $(CHECK_BUILD)
$(SYSTEMTAP_RUNTIME)/linux/autoconf-linux-sched_headers.c 1>&2; then echo
"#define STAPCONF_LINUX_SCHED_HEADERS 1"; echo "yes"; else echo "no"; fi >> $@
~~~
--
You are receiving this mail because:
You are the assignee for the bug.