You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When <=dev-libs/libgit2-0.22.2 is installed, cargo fails to build:
/tmp/portage/portage/dev-rust/cargo-0.2.0/homedir/.cargo/registry/src/github.ghproxy.top-1ecc6299db9ec823/git2-0.2.9/src/call.rs:14: undefined reference to `git_config_get_string_buf'
git_config_get_string_buf was recently added to libgit2 and is not present in libgit2-0.22.2.
I assume during the build of libgit2-sys the libgit2 library inside libgit2-sys is used for compilation.
When cargo is finally build and in its link-phase, the system libgit2.so is used instead.
This results in the linking error above.
My conclusion is that order of the library paths is not correct in the final call to cc:
When <=dev-libs/libgit2-0.22.2 is installed, cargo fails to build:
/tmp/portage/portage/dev-rust/cargo-0.2.0/homedir/.cargo/registry/src/github.ghproxy.top-1ecc6299db9ec823/git2-0.2.9/src/call.rs:14: undefined reference to `git_config_get_string_buf'
git_config_get_string_buf was recently added to libgit2 and is not present in libgit2-0.22.2.
I assume during the build of libgit2-sys the libgit2 library inside libgit2-sys is used for compilation.
When cargo is finally build and in its link-phase, the system libgit2.so is used instead.
This results in the linking error above.
My conclusion is that order of the library paths is not correct in the final call to cc:
The text was updated successfully, but these errors were encountered: