[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH, dejagnu] Log file renaming
From: |
Thomas Preudhomme |
Subject: |
[PATCH, dejagnu] Log file renaming |
Date: |
Fri, 10 Mar 2017 14:57:45 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 |
Hi,
One confusing thing for people new to GCC trying to reproduce a
testcase failure for arm-none-eabi targets is the origin of the
gcc_tg.o file linked in all execution testcases. It cannot be found in
the build tree and there is no mention of its building in the log file.
As mentioned in [1], it's gcc-testglue.o renamed and the log do mention
how to build that file. However, the renaming itself is not logged.
[1] https://gcc.gnu.org/ml/gcc/2013-10/msg00246.html
This patch adds a logging message to the remote_download procedure in
dejagnu so that people can see the origin of files which are downloaded
or renamed.
ChangeLog entry is as follows:
2017-03-03 Thomas Preud'homme <address@hidden>
* lib/remote.exp (remote_download): Add logging message when source
and destination file differ in name.
Running GCC testsuite with this patch shows the expected message in the log.
Best regards,
Thomas
log_file_renaming.patch
Description: Text Data
- [PATCH, dejagnu] Log file renaming,
Thomas Preudhomme <=