diff options
author | Alan Modra <amodra@gmail.com> | 2024-08-29 12:00:17 +0930 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2024-08-29 21:05:57 +0930 |
commit | 9459f695d3b79ac5509d8da8b1f4f7d68d91e840 (patch) | |
tree | 00804b18c14e075c842850c193a8bd5fff15d5e3 /binutils/dwarf.c | |
parent | 35e273526b7d4e345bb77a042af093508dad57f4 (diff) | |
download | binutils-9459f695d3b79ac5509d8da8b1f4f7d68d91e840.zip binutils-9459f695d3b79ac5509d8da8b1f4f7d68d91e840.tar.gz binutils-9459f695d3b79ac5509d8da8b1f4f7d68d91e840.tar.bz2 |
ld testsuite output files
In many cases the output of one run_cc_link_tests test is used as
input for another test. I hit a case where some system change caused
errors when compiling object files, but the old .so output from a
previous test run was still there, and then was used in following
tests.
* testsuite/lib/ld-lib.exp (run_ld_link_tests): Delete output
file before building.
(run_ld_link_exec_tests, run_cc_link_tests): Likewise.
Diffstat (limited to 'binutils/dwarf.c')
0 files changed, 0 insertions, 0 deletions