diff options
| author | Alan Modra <amodra@gmail.com> | 2025-08-26 19:19:44 +0930 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2025-08-27 21:45:12 +0930 |
| commit | 3fa891a80c5faba051afb0e6607f6b347bf61f9a (patch) | |
| tree | d63a8c3fa100388170493ef50da8d50f7db40cb5 /gdb/python/python.c | |
| parent | ab0e81e536b85d40569df79d1872c1e1f4dda1af (diff) | |
| download | binutils-3fa891a80c5faba051afb0e6607f6b347bf61f9a.zip binutils-3fa891a80c5faba051afb0e6607f6b347bf61f9a.tar.gz binutils-3fa891a80c5faba051afb0e6607f6b347bf61f9a.tar.bz2 | |
objcopy "Unable to recognise the format of the input file"
This bogus error comes up when trying something like
objcopy -O binary .../binutils/testsuite/binutils-all/tek2.obj xxx
This is an annoying message, as HJ said in
https://sourceware.org/pipermail/binutils/2002-August/021354.html
and removed it for some cases, eg. I can make it go away by specifying
-I tekhex. The message is also untrue, as objcopy does in fact know
the format of the input file.
I think the message should be limited to ELF input files that are
being handled by the elf64-little, elf64-big, elf32-little or
elf32-big targets, due to libbfd being compiled with limited target
support. I'm also changing the message a litle.
* objcopy.c (copy_object): Change "Unable to recognise format"
message to "Unable to recognise architecture" and only report
this error for ELF objects lacking their proper target support.
* testsuite/binutils-all/x86-64/x86-64.exp: Update to suit.
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions