ld: in util/libinftestutil.a(libinfinity-0.7.la), archive member 'libinfinity-0.7.la' with length 1080 is not mach-o or llvm bitcode file 'util/libinftestutil.a' for architecture x86_64

[ryandesign]

I've updated libinfinity in MacPorts to 0.7.2 and it builds on OS X 10.7 thru macOS 12 but not on macOS 13, where it fails with:

ld: in util/libinftestutil.a(libinfinity-0.7.la), archive member 'libinfinity-0.7.la' with length 1080 is not mach-o or llvm bitcode file 'util/libinftestutil.a' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [inf-test-certificate-request] Error 1
make[3]: *** Waiting for unfinished jobs....

Here is the log from the MacPorts automated build system: libinfinity.log.gz

I have in my notes that we encountered a similar error years ago when attempting to build an older version of libinfinity for multiple architectures simultaneously (a "universal" build):

/usr/bin/ranlib: library member: libinftestutil.a(libinfinity-0.5.la) is not an object file (not allowed in a library with multiple architectures)

If that's the same problem, then it looks like as of macOS 13 this has become a problem for the more typical single-architecture builds as well.

[pkern]

Well, the .la file is libtool's metadata file. It shouldn't land in the .a archive in the first place and it's technically not even needed. You should be able to look at how other libtool-using things do it.

[ryandesign]

Well, here's what the libinfinity build system is running:

rm -f libinftestutil.a
ar cru libinftestutil.a libinftestutil_a-inf-test-util.o ../../libinfinity/libinfinity-0.7.la ../../libinftext/libinftext-0.7.la
ranlib libinftestutil.a

[pkern]

TBH I don't really think it's that much Gobby-specific and more of a question for the MacPorts bug tracker. You might need to do libtoolize with Apple's toolchain.