From: Julien Grall <julien.grall@linaro.org>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
Julien Grall <julien.grall@linaro.org>,
ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com
Subject: [PATCH] Use non-debug build for Xen 4.10
Date: Wed, 29 Nov 2017 12:09:40 +0000 [thread overview]
Message-ID: <20171129120940.20835-1-julien.grall@linaro.org> (raw)
Modify Config.mk and Kconfig.debug to disable debug by default in
preparation for late RCs and eventual release.
Signed-off-by: Julien Grall <julien.grall@linaro.org>
---
I would like this to get included before branching. So we can cut the RC
right after branching.
---
tools/Rules.mk | 2 +-
xen/Kconfig.debug | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/Rules.mk b/tools/Rules.mk
index 61515d3063..6268c14e3a 100644
--- a/tools/Rules.mk
+++ b/tools/Rules.mk
@@ -31,7 +31,7 @@ CFLAGS_xeninclude = -I$(XEN_INCLUDE)
XENSTORE_XENSTORED ?= y
# A debug build of tools?
-debug ?= y
+debug ?= n
debug_symbols ?= $(debug)
# Set CONFIG_GOLANG=y in .config (or in make) to build golang
diff --git a/xen/Kconfig.debug b/xen/Kconfig.debug
index 8d70f63743..c0f3c017ed 100644
--- a/xen/Kconfig.debug
+++ b/xen/Kconfig.debug
@@ -3,7 +3,7 @@ menu "Debugging Options"
config DEBUG
bool "Developer Checks"
- default y
+ default n
---help---
If you say Y here this will enable developer checks such as asserts
and extra printks. This option is intended for development purposes
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2017-11-29 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:09 Julien Grall [this message]
2017-11-29 13:29 ` [PATCH] Use non-debug build for Xen 4.10 Jan Beulich
2017-11-29 14:22 ` Julien Grall
2017-11-29 14:27 ` Jan Beulich
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=20171129120940.20835-1-julien.grall@linaro.org \
--to=julien.grall@linaro.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).