[MacPorts] #64253: llvm-3.3 and llvm-3.4 fail for ppc+ppc64

MacPorts noreply at macports.org
Fri Dec 24 09:03:17 UTC 2021


#64253: llvm-3.3 and llvm-3.4 fail for ppc+ppc64
-------------------------------+-------------------------------------------
  Reporter:  barracuda156      |      Owner:  (none)
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.7.1
Resolution:                    |   Keywords:  PowerPC, Leopard, ppc64, LLVM
      Port:  llvm-3.3,         |
  llvm-3.4                     |
-------------------------------+-------------------------------------------

Comment (by barracuda156):

 Replying to [comment:3 ryandesign]:
 > Looks like `ar` is used to create libLLVMCodeGen.a and then `ranlib` is
 asked to operate on that static library and complains about how it was
 made. I have often seen the recommendation that static libraries should be
 created using `libtool`, not `ar`. I don't know if that would solve this
 particular issue. If you can figure out how to tell llvm to use `libtool`
 instead of `ar` you could try that.

 There are some posts online apparently addressing the issue, however they
 don't seem to work. For example, this is specifically for llvm:
 https://reviews.llvm.org/rG6108658da4c2cef2d303c6a2fddfb60a5d589e69 (fails
 anyway).

 AR is defined in Makefile.config.in and AR.Flags defined in
 Makefile.rules. I can patch these to use Libtool, but I don't know which
 flags to use.
 I tried "-static -o" from here: https://patchwork.kernel.org/project/qemu-
 devel/patch/1462236478-61645-2-git-send-email-chrisfriedt at gmail.com - and
 it failed too.

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


More information about the macports-tickets mailing list