Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[libb2] uses wrong install name in arm64-osx-dynamic triplet #31719

Closed
liviaerxin opened this issue May 30, 2023 · 1 comment
Closed

[libb2] uses wrong install name in arm64-osx-dynamic triplet #31719

liviaerxin opened this issue May 30, 2023 · 1 comment
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. Stale

Comments

@liviaerxin
Copy link
Contributor

liviaerxin commented May 30, 2023

Describe the bug
[libb2] uses an absolute install name in arm64-osx-dynamic triplet

Environment

  • OS: arm64 osx
  • Compiler: clang

To Reproduce
Steps to reproduce the behavior:

  1. vcpkg remove libb2:arm64-osx-dynamic
  2. vcpkg install libb2 --host-triplet=arm64-osx-dynamic --triplet=arm64-osx-dynamic --no-binarycaching

Current behavior

❯ otool -L /opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib
/opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib:
	/opt/vcpkg/installed/arm64-osx-dynamic/lib/libb2.1.dylib (compatibility version 2.0.0, current version 2.4.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)

Expected behavior

❯ otool -L /opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib
/opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib:
	@rpath/libb2.1.dylib (compatibility version 2.0.0, current version 2.4.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)

and includes @loader_path as its @rpath.

❯ otool -l /opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib | grep -A5 LC_RPATH
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants