-
Notifications
You must be signed in to change notification settings - Fork 34
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
CentOS 7 Build issue #65
Comments
what is libcurl version? |
can you share the full output file (output-file ~/.opam/log/ocurl-22838-326a35.out) because what is shown above is warnings, shouldn't be the reason of failure |
Thanks for the response! libcurl 7.29.0, output below:
|
Happy new year! Do you have any thoughts about this error? |
please check if building from git master works |
Cloning and pinning seems to result in a curl dependency issue with
|
Similar issues here. libcurl version 7.68 on Debian bullseye. ....... edit ....... This actually seems to be a Mint install as a vm not debian ( not my computer ) The opam package gives this error.
Using the latest git code I get this.
|
So sorry to bump this but just wondering if this is something that could still be resolved? |
Any news here? Running into the same issues as Matthew above. My C++ is non-existent, and I'd rather not manually patch code retrieved from repositories by people way smarter than me ;) |
this is unrelated, it means libcurl4-*-dev package is not installed |
If i pin ocurl to master then i see a dependency issue. Seems to me that it's expecting curl to return a version greater than 0.9.2 but instead its getting ~dev, and failing.
If i edit the ocurl.opam file, remove the curl version constraint and then install curl first (separately to ocurl) then everything seems to install and work successfully.
In any other order, or installing curl togethor with ocurl fails with the version matching problem. Any thoughts? |
OP issue with CentOS is fixed I believe. |
Having difficulty installing ocurl on CentOS 7 (as a dependency of liquidsoap 2.1.3). Here's the results from a new blank switch (4.12.1)
I've attempted to pin the latest as suggested from #63 but this has resulted in another problem:
The text was updated successfully, but these errors were encountered: