aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-09-06 09:33:18 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2024-10-03 19:33:55 +0200
commitf9423e9f0ad14b186c65d6eb207438d2eddd24ea (patch)
treefdd3a142b82913109d5c62ea75c0f8439821b492 /scripts
parented76671888676792493320db53ed773a108cbd45 (diff)
downloadqemu-f9423e9f0ad14b186c65d6eb207438d2eddd24ea.zip
qemu-f9423e9f0ad14b186c65d6eb207438d2eddd24ea.tar.gz
qemu-f9423e9f0ad14b186c65d6eb207438d2eddd24ea.tar.bz2
minikconf: print error entirely on stderr
While debugging an invalid configuration, I noticed that the clauses debug ends up on stderr but the header ("The following clauses were found..." ends up on stdout. This makes the contents of meson-logs/meson-log.txt a bit confusing. Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/minikconf.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/minikconf.py b/scripts/minikconf.py
index bcd9101..6f7f43b 100644
--- a/scripts/minikconf.py
+++ b/scripts/minikconf.py
@@ -112,7 +112,7 @@ class KconfigData:
def set_value(self, val, clause):
self.clauses_for_var.append(clause)
if self.has_value() and self.value != val:
- print("The following clauses were found for " + self.name)
+ print("The following clauses were found for " + self.name, file=sys.stderr)
for i in self.clauses_for_var:
print(" " + str(i), file=sys.stderr)
raise KconfigDataError('contradiction between clauses when setting %s' % self)