From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/25266] New: Log configure command output when compiling modules
Date: Tue, 10 Dec 2019 06:12:00 -0000 [thread overview]
Message-ID: <bug-25266-6586@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2019-12-10 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 6:12 craig.ringer at 2ndquadrant dot com [this message]
2019-12-10 6:12 ` [Bug runtime/25266] " craig.ringer at 2ndquadrant dot com
2019-12-10 6:24 ` craig.ringer at 2ndquadrant dot com
2019-12-12 20:30 ` fche at redhat dot com
2019-12-13 4:56 ` craig.ringer at 2ndquadrant dot com
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-25266-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).