Issues with objdump and objcopy on Mac M1

objdump seems to always print an error message, example:

malcolm@Malcolms-Air keeperfx % objdump --version
Apple LLVM version 13.0.0 (clang-1300.0.29.30)
 Optimized build.
 Default target: arm64-apple-darwin21.3.0
 Host CPU: vortex

 Registered Targets:
  aarch64  - AArch64 (little endian)
  aarch64_32 - AArch64 (little endian ILP32)
  aarch64_be - AArch64 (big endian)
  arm    - ARM
  arm64   - ARM64 (little endian)
  arm64_32  - ARM64 (little endian ILP32)
  armeb   - ARM (big endian)
  thumb   - Thumb
  thumbeb  - Thumb (big endian)
  x86    - 32-bit X86: Pentium-Pro and above
  x86-64   - 64-bit X86: EM64T and AMD64
malcolm@Malcolms-Air keeperfx % clang --version
Apple clang version 13.0.0 (clang-1300.0.29.30)
Target: arm64-apple-darwin21.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
malcolm@Malcolms-Air keeperfx % clang -c src/actionpt.c
In file included from src/actionpt.c:19:
In file included from src/actionpt.h:22:
src/bflib_basics.h:153:15: warning: '__stdcall' calling convention is not supported for this target [-Wignored-attributes]
typedef void (__stdcall *TbNetworkCallbackFunc)(struct TbNetworkCallbackData *, void *);
       ^
1 warning generated.
malcolm@Malcolms-Air keeperfx % objdump -f actionpt.o 

actionpt.o:	file format mach-o arm64

/Library/Developer/CommandLineTools/usr/bin/objdump: error: 'actionpt.o': Invalid/Unsupported object file format

The warning message should have no impact on objdumps ability to produce a result.

I have been looking for objcopy as I need to rename some functions in a precompiled library. I installed the gnu binutils version (brew install binutils) .. this generates a file that the gnu binutils thinks is perfect. The Apple objdump throws up error messages.