[erlang-questions] Erlang compilation travails
Gokhan Boranalp
kunthar@REDACTED
Wed May 7 09:28:50 CEST 2014
See here:
http://docs.basho.com/riak/latest/ops/building/installing/erlang/#Installing-on-GNU-Linux
Use this command to install the required dependency packages:
sudo apt-get install build-essential libncurses5-dev openssl
libssl-dev fop xsltproc unixodbc-dev
On Wed, May 7, 2014 at 7:31 AM, Bob Ippolito <bob@REDACTED> wrote:
> The thing that makes the most sense here is that you've included the stack
> trace. It says crypto can't start. My guess is that you didn't have OpenSSL
> headers installed when this Erlang was built.
>
> On Tuesday, May 6, 2014, <lloyd@REDACTED> wrote:
>>
>> Hi Garrett,
>>
>> You're making more sense by the minute.
>>
>> Just tried to install rebar under my brand-spanking-new kerl Erlang
>> installation on my Debian Wheezy box and ran into the same ol' same ol':
>>
>> lloyd@REDACTED:~/Erl/Tools$ cd rebar
>> lloyd@REDACTED:~/Erl/Tools/rebar$ ./bootstrap
>> Recompile: src/rebar
>> Recompile: src/rebar_abnfc_compiler
>> Recompile: src/rebar_app_utils
>> Recompile: src/rebar_appups
>> ...
>> Recompile: src/rebar_upgrade
>> Recompile: src/rebar_utils
>> Recompile: src/rebar_xref
>> Uncaught error in rebar_core: {'EXIT',
>> {undef,
>> [{crypto,start,[],[]},
>> {rebar,run_aux,2,
>> [{file,"src/rebar.erl"},{line,165}]},
>> {rebar,main,1,
>> [{file,"src/rebar.erl"},{line,58}]},
>> {erl_eval,do_apply,6,
>> [{file,"erl_eval.erl"},{line,657}]},
>> {escript,eval_exprs,5,
>> [{file,"escript.erl"},{line,865}]},
>> {erl_eval,local_func,5,
>> [{file,"erl_eval.erl"},{line,544}]},
>> {escript,interpret,4,
>> [{file,"escript.erl"},{line,781}]},
>> {escript,start,1,
>> [{file,"escript.erl"},{line,276}]}]}}
>> lloyd@REDACTED:~/Erl/Tools/rebar$
>>
>>
>> So, maybe it's not me after all, though I wouldn't discount. But, if
>> indeed not due to my fuzzy-headed fumble-fingers then perhaps, at least, my
>> tsuris will alert some packager that there's trouble on the farm.
>>
>> Thanks, Dude.
>>
>> Lloyd
>>
>>
>>
>> -----Original Message-----
>> From: "Garrett Smith" <g@REDACTED>
>> Sent: Tuesday, May 6, 2014 6:24pm
>> To: "Lloyd Prentice" <lloyd@REDACTED>
>> Cc: "Erlang-Questions Questions" <erlang-questions@REDACTED>
>> Subject: Re: [erlang-questions] Erlang compilation travails
>>
>> On Tue, May 6, 2014 at 5:03 PM, <lloyd@REDACTED> wrote:
>> > Hello,
>> >
>> > I've been working my way up the Erlang learning curve for several years
>> > now quite cheerfully--- coding, installing, compiling, uninstalling, etc.
>> > But over the past several days my attempts to install n2o/samples have
>> > thrown crash dumps at the very last stages of compilation.
>> >
>> > Thinking the problem may be an hardware, OS, or Erlang installation
>> > issue, I moved to another box running Debian Wheezy. But on this box
>> > installation of rebar fails in the ./bootstrap step. Moved to second Debian
>> > box--- same issue.
>> >
>> > The only common denominator is and upgrade of Ubuntu to 14.04 on box one
>> > and installation of Erlang under kerl on all three boxes.
>> >
>> > Been at this all day trying to get to the root of the problem. Decided
>> > to go back to basics and COMPLETELY uninstall Erlang, rebar, and kerl from
>> > the first Debian box and reinstall Erlang and rebar from scratch.
>> >
>> > But here's the mystery:
>> >
>> > lloyd@REDACTED:~$ sudo apt-get --purge remove 'erlang*'
>> > lloyd@REDACTED:~$ sudo dpkg-query -l 'erlang*'
>> > dpkg-query: no packages found matching erlang*
>> > lloyd@REDACTED:~$ sudo dpkg-query -l kerl
>> > dpkg-query: no packages found matching kerl
>> > lloyd@REDACTED:~$ sudo dpkg-query -l rebar
>> > dpkg-query: no packages found matching rebar
>> > lloyd@REDACTED:~$ cd .kerl
>> > bash: cd: .kerl: No such file or directory
>> > lloyd@REDACTED:~$ whereis erlang
>> > erlang:
>> > lloyd@REDACTED:~$ whereis rebar
>> > rebar:
>> > lloyd@REDACTED:~$ whereis kerl
>> > kerl:
>> > lloyd@REDACTED:~$ cd /usr/local/bin
>> > lloyd@REDACTED:/usr/local/bin$ ls -l
>> > total 0
>>
>> > lloyd@REDACTED:~$ cd ~
>> > lloyd@REDACTED:~$ erl
>> > Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:2:2] [async-threads:10]
>> > [hipe] [kernel-poll:false]
>> >
>> > Eshell V6.0 (abort with ^G)
>> > 1>
>> >
>> > Yikes! After all that house-cleaning, erl still runs!
>> >
>> > So my question: In which dark corner of my directory tree is erl still
>> > lurking?
>> >
>> > Bonus question: Am I being a stupid dunderhead at somewhere along the
>> > line or my computers IPIO (Inate Perversion of Inanimate Objects) deamons?
>> >
>> > Help!
>>
>> It may be a pointless sacrifice to the Gods of Superstition -- there
>> may in fact not be problem -- but lore has it that the system packages
>> for Erlang are notoriously fickle, especially where Erlang is split up
>> into dozens and dozens of dependent packages as they are for Ubuntu.
>>
>> I personally would not spend a single minute troubleshooting a
>> problematic Ubuntu Erlang installation. Rather, I'd uninstall it and
>> compile Erlang from source and use that version via "sudo make
>> install". It takes a while, but I bet it takes a lot less time than
>> figuring out the Ubuntu problem.
>>
>> This article from the nice folks at Basho will help you compile on Ubuntu:
>>
>> http://docs.basho.com/riak/latest/ops/building/installing/erlang/
>>
>> But I could be wrong -- I'm just sayin' what I'd do here :)
>>
>> Garrett
>>
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
--
BR,
\|/ Kunthar
More information about the erlang-questions
mailing list