-
Notifications
You must be signed in to change notification settings - Fork 454
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
[BUILD] CURL versions discrepancies with bazel #2520
Comments
Bonjour @ecourreges-orange Please double check which version of curl headers are used, and which version of the curl library is used to link, in your build: I suspect a discrepancy there. See comments in the PR. |
Bonjour @marcalff opentelemetry-cpp/bazel/repository.bzl Line 152 in d32f960
In the cmake build, the user brings his own curl version. I am running an apache module which is dynamically loaded, I can't afford to have a different curl than the system, because other apache modules probably use libcurl of the system. An ldd of my app confirms that curl is loaded dynamically from the system, which causes the version discrepancy. As far as the solutions, I suppose the bazel build could use the system curl if it founds it, instead of downloading it? |
Thanks for the details. This issue needs to stay opened, to see how to address bazel. |
For now I have a working version in my "nobazelcurl" fork, replacing libcurl deps like this to use the system version of curl.
https://github.com/ecourreges-orange/opentelemetry-cpp/blob/nobazelcurl/bazel/systemcurl.BUILD
|
This issue was marked as stale due to lack of activity. |
Describe your environment
Ubuntu 20.04 with its curl/libcurl v 7.68.0-1ubuntu2.21
bazel 5.4.1
Steps to reproduce
Created an OtlpHttpExporter
What is the expected behavior?
No problem connecting, unsupported options not being used
What is the actual behavior?
20312 is CURLOPT_PREREQFUNCTION you can see here that it is supported in curl 7.80.0 and above, although otlp exporter tries to use it for 7.5 and above which is exactly my case for producing the bug 7.5<7.68<7.80
So I think simply changing the test for the curl version will fix this bug, and I will post a PR for that in a couple of minutes.
opentelemetry-cpp/ext/include/opentelemetry/ext/http/client/curl/http_operation_curl.h
Line 105 in d32f960
opentelemetry-cpp/ext/src/http/client/curl/http_operation_curl.cc
Line 155 in d32f960
opentelemetry-cpp/ext/src/http/client/curl/http_operation_curl.cc
Line 1047 in d32f960
The other option CURLOPT_PREREQDATA which is also concerned appeared in the same curl version 7.80.0, so all should be fine in one fix.
Not sure I can unit test that though...
The text was updated successfully, but these errors were encountered: