diff options
| author | Pedro Alves <pedro@palves.net> | 2022-06-07 20:11:32 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2022-06-08 14:06:38 +0100 |
| commit | bc2220c89de813bf67d4172a4c483d1e2b843366 (patch) | |
| tree | 3dcd343082bab566d49080f7745a51d7e5fe8d2b /gdb/testsuite/lib/gdb-python.exp | |
| parent | 57698478b75319a962b899c3f8d3a03baa5eaab4 (diff) | |
| download | gdb-bc2220c89de813bf67d4172a4c483d1e2b843366.zip gdb-bc2220c89de813bf67d4172a4c483d1e2b843366.tar.gz gdb-bc2220c89de813bf67d4172a4c483d1e2b843366.tar.bz2 | |
aarch64: Add fallback if ARM_CC_FOR_TARGET not set
On Aarch64, you can set ARM_CC_FOR_TARGET to point to the 32-bit
compiler to use when testing gdb.multi/multi-arch.exp and
gdb.multi/multi-arch-exec.exp. If you don't set it, then those
testcases don't run.
I guess that approximately nobody remembers to set ARM_CC_FOR_TARGET.
This commit adds a fallback. If ARM_CC_FOR_TARGET is not set, and
testing for Linux, try arm-linux-gnueabi-gcc,
arm-none-linux-gnueabi-gcc, arm-linux-gnueabihf-gcc as 32-bit
compilers, making sure that the produced executable runs on the target
machine before claiming that the compiler produces useful executables.
Change-Id: Iefe5865d5fc84b4032eaff7f4c5c61582bf75c39
Diffstat (limited to 'gdb/testsuite/lib/gdb-python.exp')
0 files changed, 0 insertions, 0 deletions