[MacPorts] #68226: openmpi-default @4.1.4: error: Could not determine global symbol label prefix

[MacPorts]

#68226: openmpi-default @4.1.4: error: Could not determine global symbol label
prefix
------------------------------+----------------------
  Reporter:  chaochinyang     |      Owner:  mascguy
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.8.1
Resolution:                   |   Keywords:  ventura
      Port:  openmpi-default  |
------------------------------+----------------------

Comment (by mmphys):

 I have the same failure (on arm64 fwiw).


 {{{
 :info:configure configure: error: Could not determine global symbol label
 prefix

 }}}

 Seemingly because of an objdump failure 4 lines earlier in the log

 {{{
 :info:configure checking if .note.GNU-stack is needed...
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump:
 error: 'conftest.o': Invalid/Unsupported object file format

 }}}

 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?)

 This fails on any object file, even an empty command line tool project,
 e.g.:

 {{{
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump
 --file-headers main.o

 main.o: file format mach-o arm64
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump:
 error: 'main.o': Invalid/Unsupported object file format

 }}}

 I've submitted a bug report to Apple re objdump in Xcode 15.

 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?

-- 
Ticket URL: <https://trac.macports.org/ticket/68226#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS