Re: Syntax error: word unexpected (expecting ")" ) when cross compiling
| Newsgroups | gmane.comp.lang.erlang.bugs |
|---|---|
| Message-ID | <OF78ACFB91.48159E44-ON85257D19.0058A0F9-86257D19.00597E11@apcc.com> |
[email protected] wrote on 07/18/2014 12:57:32 AM: > Du Felix <[email protected]> > Sent by: [email protected] > > 07/18/2014 12:57 AM > > To > > [email protected], > > cc > > Subject > > [erlang-bugs] Syntax error: word unexpected (expecting ")" ) when > cross compiling > > Hi everyone. > I did a cross compiling with the command: > ./configure --host=arm-linux-gnueabif > Duiring compilation, I got such error: > > === Entering application hipe > make[3]: Entering directory `/home/dmy/App/otp_src_17.0/lib/hipe/misc' > ERLC ../ebin/hipe_consttab.beam > /home/dmy/App/otp_src_17.0/bootstrap/bin/erlc: 1: > /home/dmy/App/otp_src_17.0/bootstrap/bin/erlc: Syntax error: word > unexpected (expecting ")") > make[3]: *** [../ebin/hipe_consttab.beam] Error 2 > make[3]: Leaving directory `/home/dmy/App/otp_src_17.0/lib/hipe/misc' > make[2]: *** [opt] Error 2 > make[2]: Leaving directory `/home/dmy/App/otp_src_17.0/lib/hipe' > make[1]: *** [opt] Error 2 > make[1]: Leaving directory `/home/dmy/App/otp_src_17.0/lib' > make: *** [secondary_bootstrap_build] Error 2 > > When I went to /home/dmy/App/otp_src_17.0/lib/hipe/ebin, I didn't > find hipe_consttab.beam. > > I could successfully compiled a x86 erlang on my linux mint, but > got that error while cross compling. Cross compiling to ARM is a little involved. See if either of these projects meet your needs: Nerves: http://nerves-project.org/ Is based on Buildroot. If Erlang is the only thing you are putting on your ARM image, then this is a good option Yocto: http://www.yoctoproject.org/ https://github.com/joaohf/meta-erlang Yocto is arguably more full featured, but some assembly is required. See joahf's layer for adding Erlang to a build. It is fairly easy to modify his source to point to a newer release if you need it. I believe both projects have to patch the OTP source in order to build correctly. Hope that helps, Mike _______________________________________________ erlang-bugs mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-bugs