Skip to content
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

abc doesn't work with saw-remote-api container #1647

Closed
weaversa opened this issue Apr 29, 2022 · 3 comments
Closed

abc doesn't work with saw-remote-api container #1647

weaversa opened this issue Apr 29, 2022 · 3 comments
Labels
subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings

Comments

@weaversa
Copy link
Contributor

My guess is that this is because abc is built in what4-solvers to rely on some shared libraries such as libreadline, but which are not present in the saw-remote-api container. Since the binaries are copied from the what4-solvers release into the saw-remote-api container, abc can't find those shared libraries.

https://github.com/GaloisInc/saw-script/blob/master/saw-remote-api/Dockerfile

@RyanGlScott
Copy link
Contributor

Good catch. I think adding libreadline-dev to the list of packages installed in saw-remote-api's Dockerfile should fix this issue, similarly to how it's done in saw's Dockerfile.

@weaversa
Copy link
Contributor Author

Perfect! Thank you!

weaversa added a commit that referenced this issue Apr 29, 2022
Addling libreadline to support abc. closes #1647
@RyanGlScott RyanGlScott added the subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings label May 2, 2022
@RyanGlScott
Copy link
Contributor

Fixed in #1652.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants