From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] gdb/selftest.m4: ensure $development is set
Date: Thu, 12 Mar 2020 12:07:38 -0600 [thread overview]
Message-ID: <87h7ytjvkl.fsf@tromey.com> (raw)
In-Reply-To: <20200305193011.25939-1-simon.marchi@efficios.com> (Simon Marchi's message of "Thu, 5 Mar 2020 14:30:08 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> The GDB build in non-development mode (turn development to false in
Simon> bfd/development.sh if you want to try) is currently broken:
[...]
FWIW I read through this series and it all looked ok to me.
Thank you for doing this.
Tom
next prev parent reply other threads:[~2020-03-12 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 19:30 Simon Marchi
2020-03-05 19:30 ` [PATCH 3/4] Don't include selftests objects in build when unit tests are disabled Simon Marchi
2020-03-05 19:30 ` [PATCH 2/4] Move sourcing of development.sh to GDB_AC_COMMON Simon Marchi
2020-03-05 19:30 ` [PATCH 4/4] Move gdb/selftest.m4 to gdbsupport/selftest.m4 Simon Marchi
2020-03-05 19:42 ` [PATCH 1/4] gdb/selftest.m4: ensure $development is set Simon Marchi
2020-03-12 18:07 ` Tom Tromey [this message]
2020-03-12 18:19 ` Simon Marchi
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=87h7ytjvkl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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