Opened 4 years ago

Closed 4 years ago

#61853 closed defect (duplicate)

libsecret @0.20.4: llvm-objdump: Unknown command line argument '-macho'

Reported by: MStraeten (Martin Straeten) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: bigsur Cc:
Port: libsecret

Description (last modified by ryandesign (Ryan Carsten Schmidt))

--->  Building libsecret
Error: Failed to build libsecret: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_libsecret/libsecret/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port libsecret failed

failed while rebuilding after purging my old macports installation, my build from 15.11.2020 was successful (big sur, sdk 11.1 + Xcode 12.??)

Attachments (1)

main.log (406.7 KB) - added by MStraeten (Martin Straeten) 4 years ago.

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by MStraeten (Martin Straeten)

Attachment: main.log added

comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Summary: libsecret @0.20.4 (gnome) build fails with commandline tools for XCode 12.3libsecret @0.20.4: llvm-objdump: Unknown command line argument '-macho'

The error in the log is:

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'?
Traceback (most recent call last):
  File "/opt/local/bin/g-ir-scanner", line 99, in <module>
    sys.exit(scanner_main(sys.argv))
  File "/opt/local/lib/gobject-introspection/giscanner/scannermain.py", line 579, in scanner_main
    shlibs = create_binary(transformer, options, args)
  File "/opt/local/lib/gobject-introspection/giscanner/scannermain.py", line 419, in create_binary
    shlibs = resolve_shlibs(options, binary, options.libraries)
  File "/opt/local/lib/gobject-introspection/giscanner/shlibs.py", line 183, in resolve_shlibs
    _resolve_non_libtool(options, binary, non_libtool))
  File "/opt/local/lib/gobject-introspection/giscanner/shlibs.py", line 103, in _resolve_non_libtool
    output = subprocess.check_output(args)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/bin/sh', './libtool', '--mode=execute', 'otool', '-L', '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_libsecret/libsecret/work/libsecret-0.20.4/tmp-introspect4q55o017/Secret-1']' returned non-zero exit status 1.

comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: bigsur added

It sounds like otool -L is invoking llvm-objdump with the -macho, -dylibs-used, and -non-verbose flags, but that the version of llvm-objdump in the llvm-11 port does not support those flags. From https://reviews.llvm.org/D92310 it sounds like the flags might now need two leading dashes rather than one. Try deactivating the llvm-11 port. Or try reinstalling the cctools port with the +xcode variant, in case it is not already installed with that variant.

comment:3 Changed 4 years ago by kencu (Ken)

the cctools port needs to altered (again) to only use the xcode variant on all newer systems. Jeremy took that out of the port last year, but it needs to go back in, and work similarly to ld64 in choosing variants.

comment:4 Changed 4 years ago by MStraeten (Martin Straeten)

yep, by default cctools was activated with +llvm11. reinstalling it with +xcode does the job ;)

comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed

Duplicate of #61852.

Note: See TracTickets for help on using tickets.