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

Containerization fails on Intel #4

Open
DoubleMalt opened this issue Feb 10, 2016 · 1 comment
Open

Containerization fails on Intel #4

DoubleMalt opened this issue Feb 10, 2016 · 1 comment
Assignees

Comments

@DoubleMalt
Copy link
Member

https://hub.docker.com/r/cloudfleet/blimp-parachute/builds/bjpdzyfucrwbg9ngookvgzt/

setup/install-parachute.bash: line 54: /opt/cloudfleet/apps/ccl/armcl: No such file or directory

Is there no way to install lisp in a cross architectural way?

@easye
Copy link
Member

easye commented Feb 10, 2016

A complete answer to installing "lisp in a cross architectural way" would depend on the specific implementation of Common Lisp and the varying architectures one is attempting to install it upon. The specific implementation that we are installing here (CCL) is packaged to allow recompilation for varying architectures from the same source so it distinguishes its executables via naming conventions. This is perhaps not the abstraction one is used to with, say, GNU packaging but it is one possible choice. I know of no other CL implementation that takes this path while I can probably find examples of such conventions in other software systems, so this is not a property of CL implementations per se.

install-parachute.bash will abstract these concerns away when it is finished.

@easye easye self-assigned this Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants