diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2020-03-12 14:12:36 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2020-03-12 14:17:57 -0400 |
| commit | 4d696a5c686730d75623d7e41805e42ce5fcc60c (patch) | |
| tree | 077ef2a22bca4befd6b2f9088b80c7b49f703e7f /ltversion.m4 | |
| parent | 8dd8e1c7228d5dd57b3b36379718c806017988e1 (diff) | |
| download | fsf-binutils-gdb-4d696a5c686730d75623d7e41805e42ce5fcc60c.zip fsf-binutils-gdb-4d696a5c686730d75623d7e41805e42ce5fcc60c.tar.gz fsf-binutils-gdb-4d696a5c686730d75623d7e41805e42ce5fcc60c.tar.bz2 | |
gdb/selftest.m4: ensure $development is set
Before commit 3d1e5a43cbe ("gdbsupport/configure.ac: source
development.sh"), the GDB build in non-development mode (turn
development to false in bfd/development.sh if you want to try) was
broken because the gdbsupport configure script didn't source
bfd/development.sh to set the development variable.
Since the GDB_AC_SELFTEST macro relies on the `development` variable, I
propose to modify it such that it errors out if $development does not
have an expected value of "true" or "false". This could prevent a
future similar problem from happening while refactoring the configure
scripts. It would have caught the problem fixed by the patch mentioned
earlier.
gdb/ChangeLog:
* selftest.m4 (GDB_AC_SELFTEST): Error out if $development is
not "true" or "false".
* configure: Re-generate.
gdbserver/ChangeLog:
* configure: Re-generate.
gdbsupport/ChangeLog:
* configure: Re-generate.
Diffstat (limited to 'ltversion.m4')
0 files changed, 0 insertions, 0 deletions