bpstahlman
Problem with libcurl on Ubuntu
Hey I ran into another issue.
After getting cac enabled git setup on Ubuntu, when I try to run cmake it gives me an error:
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
Which seems to be related to custom built libcurl missing pthread symbols. I found some more info on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758572
Not sure if you have any ideas on how to fix this? I can check out our code, but can't build anything now (on Ubuntu).
I managed to get it working by adding a flag (--enable-threaded_resolver) to the ./configure call of libcurl.
https://github.com/bpstahlman/cac-enabled-git-setup/blob/master/build-cac-enabled-git#L716
./buildconf && ./configure --enable-threaded_resolver --with-ca-bundle="${Opts[ca-bundle-out]}" && make && $Make_install
After rebuilding the git with cac support, I was successfully able to build my cmake project. There was one side effect however, I got tons of messages saying:
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
Scott, Your analysis appears to be correct, and I really appreciate your digging into it. I definitely plan to approve the pull request. Thanks, Brett S.
On Thu, Jun 18, 2015 at 12:35 AM, Scott Przybylski <[email protected]
wrote:
I managed to git it working by adding a flag (--enable-threaded_resolver) to the ./configure call of libcurl.
https://github.com/bpstahlman/cac-enabled-git-setup/blob/master/build-cac-enabled-git#L716
./buildconf && ./configure --enable-threaded_resolver --with-ca-bundle="${Opts[ca-bundle-out]}" && make && $Make_install
After rebuilding the git with cac support, I was successfully able to build. There was one side effect however, I got tons of messages saying:
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
— Reply to this email directly or view it on GitHub https://github.com/bpstahlman/cac-enabled-git-setup/issues/2#issuecomment-113042398 .
