Skip to content

Conversation

@Haroon-Khel
Copy link
Contributor

@Haroon-Khel Haroon-Khel commented Nov 21, 2025

  • commit message has one of the standard prefixes
  • faq.md updated if appropriate
  • other documentation is changed or added (if applicable)
  • playbook changes run through VPC or QPC (if you have access)
  • VPC/QPC not applicable for this PR
  • for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

Repeating my comment #4141 (comment):

Found another solution (went a bit deep on this one). Using otool and install_tool_name I changed the path where git-remote-http looks for libcurl.4.dylib

admin@ventura-vm ~ % install_name_tool -change /usr/lib/libcurl.4.dylib /usr/local/Cellar/curl/8.17.0/lib/libcurl.4.dylib /usr/local/Cellar/git/2.52.0/libexec/git-core/git-remote-http
admin@ventura-vm ~ % otool -L /usr/local/Cellar/git/2.52.0/libexec/git-core/git-remote-http
/usr/local/Cellar/git/2.52.0/libexec/git-core/git-remote-http:
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 1226.0.0)
Changed location ----> /usr/local/Cellar/curl/8.17.0/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 9.0.0)

I thought this would mess up the signing on the git-remote-http executable since ive tampered with it but I guess not, a simple git clone command worked.

Ive tested this on an intel macos14 box, works 👍🏻 , solves:

23:15:51  git clone -q https://github.com/adoptium/TKG.git
23:15:51  dyld[2180]: Symbol not found: _curl_global_trace
23:15:51    Referenced from: <6EADC463-B41C-365C-8590-F3AE3D6E9106> /usr/local/Cellar/git/2.51.2/libexec/git-core/git-remote-http
23:15:51    Expected in:     <F8F6C7FA-6ED7-3B16-9E60-4AF09985DC3C> /usr/lib/libcurl.4.dylib
23:15:51  error: git-remote-https died of signal 6

Copy link
Member

@sxa sxa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not a great solution and we should look at seeing if we can remove it in the future since this feels like something that won't be needed for ever but I'll approve it for now given the problems we're seeing 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants