[MacPorts] #63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in .../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged
MacPorts
noreply at macports.org
Sun Oct 17 15:38:47 UTC 2021
#63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in
.../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged
---------------------------+--------------------
Reporter: ShadSterling | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.7.1
Resolution: | Keywords:
Port: libgcrypt |
---------------------------+--------------------
Comment (by ryandesign):
Replying to [ticket:63635 ShadSterling]:
> If I understand right, the universal build is building separate binaries
for arm64 and "ppc-intel" (not x86_64?), then failing to merge them into a
universal binary
Yes.
> because `lipo` doesn't understand the arm64 architecture
No. It is failing because the pkg-config files differ. The muniversal
portgroup which is used for such build-then-merge builds understands how
to merge a variety of files, but the pkg-config file format does not
accommodate any form of merging, therefore the muniversal portgroup has no
choice but to require that all the generated pkg-config files are
identical, and in this case they are not, therefore an error message must
be emitted.
This could indicate a bug in the way that the upstream build system
creates the pkg-config files. For example, in this case, the difference
appears to be in the `host` lines, but I'm not aware of any reason why a
pkg-config file should contain a `host` line, so the solution may be to
remove that line from the files.
On my system I see other pkg-config files from other ports that also have
a `host` line, so all of those ports seem to have the same bug.
--
Ticket URL: <https://trac.macports.org/ticket/63635#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list