[MacPorts] #62095: Poppler should no longer use flag -macho as newer llvms will not accept it.

[MacPorts]

#62095: Poppler should no longer use flag -macho as newer llvms will not accept it.
-----------------------+----------------------
  Reporter:  szhorvat  |      Owner:  (none)
      Type:  defect    |     Status:  reopened
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.6.4
Resolution:            |   Keywords:
      Port:  poppler   |
-----------------------+----------------------

Comment (by michaelld):

 OK some progress!

 (0) make sure you have `cctools +llvm11` installed.

 (1) Add this to the Portfile for GO-I or poppler: `build.env-append
 "GI_SCANNER_DEBUG=save-temps"`

 (2) issue `sudo port build poppler` or GO-I etc... it should fail during a
 GO-I scan

 (3) review the log for the `otool -L` command being issued; for example
 here's the one from 'poppler' that I see
 {{{
 :info:build Caught exception: <class 'subprocess.CalledProcessError'>
 CalledProcessError(1, ['otool', '-L',
 '/opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_graphics_poppler/poppler/work/build/glib
 /tmp-introspectdnhi97mq/Poppler-0.18'])
 }}}

 (4) reform and issue this command directly; from my (3) I'd do:
 {{{
 otool -L
 /opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_graphics_poppler/poppler/work/build/glib
 /tmp-introspectdnhi97mq/Poppler-0.18
 }}}
 which for me results in the following:
 {{{
 llvm-objdump: Unknown command line argument '-macho'.  Try:
 '/opt/local/libexec/llvm-11/bin/llvm-objdump --help'
 llvm-objdump: Did you mean '-h'?
 llvm-objdump: Unknown command line argument '-dylibs-used'.  Try:
 '/opt/local/libexec/llvm-11/bin/llvm-objdump --help'
 llvm-objdump: Did you mean '--dylibs-used'?
 llvm-objdump: Unknown command line argument '-non-verbose'.  Try:
 '/opt/local/libexec/llvm-11/bin/llvm-objdump --help'
 llvm-objdump: Did you mean '--non-verbose'?
 }}}

 (5) now do `sudo port install cctools +xcode` to load up a different
 `otool`

 (6) reissue the command from (4), which now for me does:
 {{{
 otool -L
 /opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_graphics_poppler/poppler/work/build/glib
 /tmp-introspectdnhi97mq/Poppler-0.18
 /opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_graphics_poppler/poppler/work/build/glib
 /tmp-introspectdnhi97mq/Poppler-0.18:
         /opt/local/lib/libpoppler-glib.8.dylib (compatibility version
 8.0.0, current version 8.19.0)
         /opt/local/lib/libpoppler.105.dylib (compatibility version
 105.0.0, current version 105.0.0)
         /opt/local/lib/libgio-2.0.0.dylib (compatibility version 5801.0.0,
 current version 5801.3.0)
         /opt/local/lib/libgobject-2.0.0.dylib (compatibility version
 5801.0.0, current version 5801.3.0)
         /opt/local/lib/libgmodule-2.0.0.dylib (compatibility version
 5801.0.0, current version 5801.3.0)
         /opt/local/lib/libglib-2.0.0.dylib (compatibility version
 5801.0.0, current version 5801.3.0)
         /opt/local/lib/libintl.8.dylib (compatibility version 10.0.0,
 current version 10.5.0)
 /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 (compatibility version 150.0.0, current version 1770.255.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1292.60.1)
 }}}

 This implies to me that the issue is actually with `cctools` and/or `llvm`
 here, since the exact same command using different variants of `cctools`
 results in success or failure.

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