diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2023-05-02 11:48:46 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2023-05-02 11:48:46 +0100 |
| commit | 4e545e3f3d600e62ed6522e0ed6ef609a6fe8354 (patch) | |
| tree | 80c038260f6916638eba754329ad5a68b2a301ba /gdb/python/py-objfile.c | |
| parent | b2499d8a40a6de13e9bc88b973a730bdf8b9b032 (diff) | |
| download | binutils-4e545e3f3d600e62ed6522e0ed6ef609a6fe8354.zip binutils-4e545e3f3d600e62ed6522e0ed6ef609a6fe8354.tar.gz binutils-4e545e3f3d600e62ed6522e0ed6ef609a6fe8354.tar.bz2 | |
gdb/testsuite: compile gdb.linespec/cp-completion-aliases.exp as C++
Noticed in passing that the prepare_for_testing call in
gdb.linespec/cp-completion-aliases.exp does not pass the 'c++' flag,
despite this being a C++ test.
I guess, as the source file has the '.cc' extension, all the compilers
are doing the right thing anyway -- the source file uses templates, so
is definitely being compiled as C++.
I noticed this when I tried to set CXX_FOR_TARGET (but not
CC_FOR_TARGET) and spotted that this script was still using the C
compiler.
Fixed in this commit by adding the 'c++' flag for prepare_for_testing.
Diffstat (limited to 'gdb/python/py-objfile.c')
0 files changed, 0 insertions, 0 deletions