Static Erlang

Grzegorz Junka list1@REDACTED
Mon Aug 3 09:13:01 CEST 2020

On 03/08/2020 06:03, Richard O'Keefe wrote:
> "Any C program can be compiled statically ..."
> Would that it were so.  However,
> - you have to have statically linkable versions of
>   all the libraries you depend one, but you might
>   have been given only .so files
> - the operating system has to be willing to run
>   statically linked programs.  My preferred operating
>   system stopped shifting libc.a and the like years
>   ago, which annoyed me greatly at the time.
> One way to package everything up so that it appears to
> someone installing it as a single file and you are
> protected to some extent from clashes whether your
> dependencies and others' is to use a container image.
> I know, bloat upon bloat.  Feh!
Unfortunately containers don't solve all the world's problems. Firstly, 
they depend on Linux kernel, secondly, they require docker or an 
alternative as a dependency when installing. An Erlang release has the 
ability to be portable without docker, e.g. easily moved across similar 
systems without depending on third party solutions.

I am essentially looking for a way of deploying an Erlang release to a 
system that doesn't have Erlang installed (and doesn't support docker).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the erlang-questions mailing list