Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

We build ZMQ locally to the erlang zmq library instead of using libzmq as built by omnibus. #200

Open
markan opened this issue May 18, 2019 · 1 comment
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Size: M A PR that changes 30-99 lines, ignoring generated files. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Chore non-critical maintenance of a project.

Comments

@markan
Copy link
Contributor

markan commented May 18, 2019

This is here for tracking before we do our next release.

We've observed that in the erlang zmq library is building a local copy of zmq instead of using the omnibus zmq. That is problematic because that is fragile and dependent on things like the python version available.

This was observed in the buildkite tests, and worked around, but should also be checked fixed for omnibus.

@PrajaktaPurohit PrajaktaPurohit added Aspect: Packaging Distribution of the projects 'compiled' artifacts. Size: M A PR that changes 30-99 lines, ignoring generated files. Type: Chore non-critical maintenance of a project. Triage: Confirmed Indicates and issue has been confirmed as described. labels Aug 23, 2019
@markan
Copy link
Contributor Author

markan commented Aug 23, 2019

To be a little more specific, building the local zmq requires python2, which is nearing end of life. The omnibus build handles this properly, and we'd like to use that instead of the unstable local build.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Aspect: Packaging Distribution of the projects 'compiled' artifacts. Size: M A PR that changes 30-99 lines, ignoring generated files. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Chore non-critical maintenance of a project.
Development

No branches or pull requests

2 participants