Skip to content

Conversation

@tjk
Copy link
Contributor

@tjk tjk commented Mar 23, 2023

GitHub is not letting me create this PR against v1.5.0.1 which is the tag I branched off of...


Edit 1: looks like need to ensure libgit2 is compiled with GIT_SSH_MEMORY_CREDENTIALS defined...

Edit 2: this may just be because it couldn't find libssh2 shared libs...

//Have library /usr/local/lib/libssh2.dylib
HAVE_LIBSSH2_MEMORY_CREDENTIALS:INTERNAL=1

Edit 3: ^ correct, this feature is disabled if libssh2 shared libs are not found (was previously building static). Not sure how to enforce or check in rugged... looking for guidance but at least for my use case this works.

@tjk
Copy link
Contributor Author

tjk commented Jun 28, 2023

Need to track why but I actually think this is the cause of libssh2/libssh2#1107... looking to see if it's something obvious.

HParker and others added 2 commits March 6, 2024 09:19
This fixes the `warning: undefining the allocator of T_DATA class Rugged::Commit` warnings that are common in ruby 3.2 builds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants