Changes between Initial Version and Version 1 of Ticket #68226, comment 4


Ignore:
Timestamp:
Oct 2, 2023, 7:34:25 AM (12 months ago)
Author:
mmphys
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #68226, comment 4

    initial v1  
    11I have the same failure (on arm64 fwiw).
    2 
    32
    43{{{
    … …  
    1413}}}
    1514
    16 I can't see the objdump command being executed by MacPorts, so I tried objdump --file-headers (which I ''think'' should work on any object file?)
    17 
    18 This fails on any object file, even an empty command line tool project, e.g.:
     15I gather MacPorts is executing objdump -x file. I tried objdump -x and --file-headers, but this fails on any object file, even an empty command line tool project, e.g.:
    1916
    2017{{{
    … …  
    2623}}}
    2724
    28 I've submitted a bug report to Apple re objdump in Xcode 15.
     25Assuming the image being checked was built by Xcode clang and is a mach-o (which is true in my case) presumably this openmpi-default configure test should use otool instead of objdump?
    2926
    30 I've since noticed objdump has the same behaviour under Xcode 14.3.1 on Ventura 13.5.2 on intel, so perhaps --file-headers is a poor test?
     27There's obviously a lot of history about objdump vs otool I'm not up to speed on ...