#52414: libarchive port fails problem with -pthread argument to clang -------------------------+-------------------- Reporter: JustinCB@… | Owner: toby@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libarchive | -------------------------+-------------------- Comment (by JustinCB@…): Replying to [comment:14 larryv@…]:
Replying to [comment:13 JustinCB@…]:
Configuring libarchive requires CMake(If it's from source). Macports CMake somehow requires libarchive.
It does not require CMake. Upstream provides an [https://github.com/libarchive/libarchive/wiki/BuildInstructions#using- configure-for-building-from-the-command-line-on-linux-freebsd-solaris- cygwin-aix-interix-mac-os-x-and-other-unix-like-systems Autotools-based build system], which is what we use.
Macports libarchive has a bug that I filed this ticket for.
Debatable. I wouldn’t be surprised if your highly unorthodox configuration were causing the issue. It isn't highly unorthodox, only slightly unorthodox. It is a part of the official macports source, but not the default. You can't use libraries you compiled yourself in macports, but you can use tools that you either compiled yourself or are included with the system(like CMake), and I was trying to build something that required CMake. It can use the CMake I compiled. I don't think this bug is in the libarchive build system, it is a bug in libtool that causes it to automatically link against the system libraries, even if you told it explicitly that you want it to link to different libraries. It might be so that it will make binaries that work on any system. It needs to do that to make binaries that work on any system because Mach-O links to a specific path instead of a path set by the environment.
-- Ticket URL: <https://trac.macports.org/ticket/52414#comment:15> MacPorts <https://www.macports.org/> Ports system for the Mac operating system