[erlang-questions] Compiling erlang with static glibc for OTP releases

Attila Rajmund Nohl attila.r.nohl@REDACTED
Tue Jun 7 20:35:59 CEST 2011

As far as I remember, if you compile libc statically, the binary will
be very much dependent on the kernel version, so the situation might
not be better...

2011/6/7, Jordan Wilberding <jwilberding@REDACTED>:
> Max,
> Were you able to come up with a fully statically compiled erlang? I am
> looking to doing the same thing.
> Thanks!
> JW
> On Mon, May 9, 2011 at 6:45 AM, Max Lapshin <max.lapshin@REDACTED> wrote:
>> I'm trying to migrate to OTP releases (using rebar) for erlyvideo.
>> Goal is to minify problems, build dependencies and package build farm.
>> I've compiled libcrypt in a static manner into erlang so, that there
>> will be no problems on different versions (debian squeeze and debian
>> sid use different versions),
>> but problems go on: different versions of libc.
>> I'm thinking about building erlang with all static dependencies so,
>> that packages from one build machine will be useable on all 64bit
>> linuxes.
>> Is it a good idea to link erlang VM with glibc static?
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list