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

Unicode.ex compile fails on armv71 #5856

Closed
alisinabh opened this issue Mar 10, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@alisinabh
Copy link

commented Mar 10, 2017

Compile of unicode.ex fails on armv71 architecture.
I've build and installed Erlang 19.2 with kerl on it. erlang seems to work fine. elixir 1.1-dev installs fine from apt but 1.4.2 wont install because of following error in make command.

Environment

  • Elixir & Erlang versions (elixir --version): Erlang/OTP 19 [erts-8.2] [source] [smp:4:4] [ds:4:4:10] [async-threads:10] [kernel-poll:false]
  • Operating system: Linux FriendlyARM 3.4.39-h3 #24 SMP PREEMPT Sat Feb 4 15:23:58 CST 2017 armv7l armv7l armv7l GNU/Linux
  • Hardware: NanoPi Neo 512mb

Current behavior

make[1]: Entering directory '/root/elixir-1.4/elixir-1.4.2'
==> unicode (compile)
Compiling unicode/unicode.ex (it's taking more than 5s)
Killed
Makefile:91: recipe for target 'lib/elixir/ebin/Elixir.String.Unicode.beam' failed
make[1]: *** [lib/elixir/ebin/Elixir.String.Unicode.beam] Error 137
make[1]: Leaving directory '/root/elixir-1.4/elixir-1.4.2'
Makefile:78: recipe for target 'lib/elixir/ebin/Elixir.Kernel.beam' failed
make: *** [lib/elixir/ebin/Elixir.Kernel.beam] Error 2

@josevalim

This comment has been minimized.

Copy link
Member

commented Mar 10, 2017

@alisinabh your OS is killing it because of lack of memory. The Unicode module requires loading large UTF tables into memory and optimizing those tables, there is not much we can do here, unfortunately. My suggestion is to use precompiled Elixir.

@josevalim josevalim closed this Mar 10, 2017

@alisinabh

This comment has been minimized.

Copy link
Author

commented Mar 10, 2017

Thank you @josevalim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.