[MacPorts] #68249: gobject-introspection @1.78.1_0+universal: FAILED: girepository/cmph/cmph-bdz-test (was: gobject-introspection-1.78.1_0+universal: FAILED: girepository/cmph/cmph-bdz-test)

[MacPorts]

#68249: gobject-introspection @1.78.1_0+universal: FAILED: girepository/cmph/cmph-
bdz-test
------------------------------------+----------------------
  Reporter:  tiuno                  |      Owner:  mascguy
      Type:  defect                 |     Status:  assigned
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:  2.8.1
Resolution:                         |   Keywords:
      Port:  gobject-introspection  |
------------------------------------+----------------------
Changes (by ryandesign):

 * status:  new => assigned
 * owner:  (none) => mascguy
 * cc: mascguy (removed)


Comment:

 Replying to [ticket:68249 tiuno]:
 > {{{
 > ld: warning: ignoring file girepository/cmph/libcmph.a, building for
 macOS-arm64 but attempting to link with file built for unknown-unsupported
 file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x23 0x31 0x2F 0x31
 0x32 0x20 0x20 0x20 )
 > Undefined symbols for architecture arm64:
 > }}}

 The undefined symbols would presumably have been in that libcmph.a archive
 that has the wrong format. Those hex bytes are:

 {{{
 !<arch>
 #1/12
 }}}

 which strikes me as unusual and not very file-format-like.

 We had a successful build of this port on all systems on our automated
 buildbot.

 From [https://build.macports.org/builders/ports-
 12_arm64-builder/builds/106599/steps/install-port/logs/stdio its log],
 this is how libcmph.a was created:

 {{{
 [24/165] rm -f girepository/cmph/libcmph.a && ar csr
 girepository/cmph/libcmph.a girepository/cmph/libcmph.a.p/bdz.c.o
 girepository/cmph/libcmph.a.p/bdz_ph.c.o
 girepository/cmph/libcmph.a.p/bmz8.c.o
 girepository/cmph/libcmph.a.p/bmz.c.o
 girepository/cmph/libcmph.a.p/brz.c.o
 girepository/cmph/libcmph.a.p/buffer_entry.c.o
 girepository/cmph/libcmph.a.p/buffer_manager.c.o
 girepository/cmph/libcmph.a.p/chd.c.o
 girepository/cmph/libcmph.a.p/chd_ph.c.o
 girepository/cmph/libcmph.a.p/chm.c.o
 girepository/cmph/libcmph.a.p/cmph.c.o
 girepository/cmph/libcmph.a.p/cmph_structs.c.o
 girepository/cmph/libcmph.a.p/compressed_rank.c.o
 girepository/cmph/libcmph.a.p/compressed_seq.c.o
 girepository/cmph/libcmph.a.p/fch_buckets.c.o
 girepository/cmph/libcmph.a.p/fch.c.o
 girepository/cmph/libcmph.a.p/graph.c.o
 girepository/cmph/libcmph.a.p/hash.c.o
 girepository/cmph/libcmph.a.p/jenkins_hash.c.o
 girepository/cmph/libcmph.a.p/miller_rabin.c.o
 girepository/cmph/libcmph.a.p/select.c.o
 girepository/cmph/libcmph.a.p/vqueue.c.o
 girepository/cmph/libcmph.a.p/vstack.c.o
 }}}

 Comparing that to your log, yours used `llvm-ar` instead of `ar`:

 {{{
 [24/165] rm -f girepository/cmph/libcmph.a && llvm-ar csrD
 girepository/cmph/libcmph.a girepository/cmph/libcmph.a.p/bdz.c.o
 girepository/cmph/libcmph.a.p/bdz_ph.c.o
 girepository/cmph/libcmph.a.p/bmz8.c.o
 girepository/cmph/libcmph.a.p/bmz.c.o
 girepository/cmph/libcmph.a.p/brz.c.o
 girepository/cmph/libcmph.a.p/buffer_entry.c.o
 girepository/cmph/libcmph.a.p/buffer_manager.c.o
 girepository/cmph/libcmph.a.p/chd.c.o
 girepository/cmph/libcmph.a.p/chd_ph.c.o
 girepository/cmph/libcmph.a.p/chm.c.o
 girepository/cmph/libcmph.a.p/cmph.c.o
 girepository/cmph/libcmph.a.p/cmph_structs.c.o
 girepository/cmph/libcmph.a.p/compressed_rank.c.o
 girepository/cmph/libcmph.a.p/compressed_seq.c.o
 girepository/cmph/libcmph.a.p/fch_buckets.c.o
 girepository/cmph/libcmph.a.p/fch.c.o
 girepository/cmph/libcmph.a.p/graph.c.o
 girepository/cmph/libcmph.a.p/hash.c.o
 girepository/cmph/libcmph.a.p/jenkins_hash.c.o
 girepository/cmph/libcmph.a.p/miller_rabin.c.o
 girepository/cmph/libcmph.a.p/select.c.o
 girepository/cmph/libcmph.a.p/vqueue.c.o
 girepository/cmph/libcmph.a.p/vstack.c.o
 }}}

 Do you have /opt/local/bin/llvm-ar on your system? If so, is it installed
 by a port (what does `port provides /opt/local/bin/llvm-ar` say?) If so,
 which port is it, and does the problem persist if you deactivate that
 port, then `sudo port clean gobject-introspection` and try again? If llvm-
 ar exists but was not provided by a port, have you used `sudo port select
 llvm` to select a version of llvm? If so, which one, and does the problem
 persist if you use `sudo port select llvm none`, then `sudo port clean
 gobject-introspection` and try again?

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