-
Notifications
You must be signed in to change notification settings - Fork 65
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
Failed to compile erlang_ale #16
Comments
Robi, Thanks for the heads-up. My 2nd gen Raspi B is coming (presently out of stock at the supplier so backordered). Once it arrives I'm trying to get a handle on this repo again :) I'll try to get this change merged in then. |
hello Josh, Very welcome :-) Right now I could step forward but another fault come :-( Compile the erlang_portutil is failing. I try to digin to it. I really would like to use this erlang extension on my Pi. So please let me know if you have done some improvements. The new fault:Compiled src/meck_expect.erl thanks, |
hello Josh, I had to install autoconf tool to the Pi:
but this does not solved all the issues. There is one left (or maybe more): It looks pihwm project uses automake, and maybe this does not looks good for the make system. I tried install the newest automake, but I have the latest: Right now I don't know what should be the next step. I hope you can turn on the light in my head :-) thanks for your help, |
hello, Just FYI, I raised a new issue on pihwm tool, due to failed compilation br, |
Just tried building it on a first gen RasPi and had no problems. Seems to be a version 2 issue. Knewter and I both are waiting to receive our RasPi2 boards so we can look into this further. |
hello rclements, Thanks for your feedback. I have read few documents about the new Pi HW and it has different CPU, more RAM, and more GPIO, than the 1st gen. HW. So the 1st 26 PIN on the 1st rev and 2nd rev HW is the same, and I though that if I use eq. GPIO-14 it should work. But If I see the error I got, it looks something is missing in my OS, so this is not that point that the GPIO access is wrong or not, I guess. I would like to ask you which OS do you use on your Pi? Maybe I can try use that, and see how it work for me. I use this OS: many thanks for your help, |
I'm running Raspbian Linux |
hello Robby, Thanks, I try download and burn into the Pi, and see how it works. thanks, |
Let me know how it goes! |
hello Robby, I have bad news :-( I could download the http://downloads.raspberrypi.org/raspbian/images/raspbian-2014-01-09/ and http://downloads.raspberrypi.org/raspbian/images/raspbian-2014-06-22/ images but Pi wont boot with these. I have to restore my original image what is running, but the ALE wont compile. thanks for your help, |
Here's another fun idea. Perhaps we could set up a pair programming session on the pi. Robby and I use tmate.io for this regularly, though we typically run it on a machine on his network then ssh into the pi together. At any rate, if we could do that then at least we could pair with you in the environment (perhaps in conjunction with a Google Hangout for voice and video) and see if we could figure out the problem for you. I'd be willing to try this tomorrow if you want. You can email me at josh dot rubyist at gmail dot com. Otherwise we'll have to wait until the pi2 arrives, and I don't even have an estimate on that date from the supplier yet sadly. |
hello Josh, I have sent an email to you from my gmail address. Unfortunately I forgot fill the subject :-( The email has detailed info about how you can login to my Pi. thanks for your help, |
I just ssh'ed into your pi, followed the README, and erlang_ale compiled fine. This is inevitably some issue with not using raspbian I guess? Anyway let me know if that sorts you out? |
hello Josh, Thanks that you have logged in to the Pi and compiled the code. I also tried once more from the beginning. Unfortunately the meck and pihwm deps are not compiled. Compiled src/gproc.erl I would like to ask you did I something wrong, or do I missed something? thanks for your help, ps: below you can see the whole logs about the compilation. All logs from the compilation= The programs included with the Debian GNU/Linux system are free software; Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent pi@raspberrypi ~ $ pwd erlang-ale -- Erlang Actor Library for EmbeddedErlang/ALE provides high level abstractions that use Erlang facilities to WarningThis is very much a work in progress and things are likely to be fragile as we Getting startedLog in to your Pi and fetch the latest version of ALE using git:
Fetch the dependencies and build erlang-ale:
You can ignore the errors generated by this. RunningUse Quick check: Turn a LED onSet a pin as an output:
Turn it on:
A more detailed usage of the GPIO module can be found in Comments and suggestions...are most welcome! Please use the issue tracker or email us at License
pi@raspberrypi ~/ethrbh/erlang-ale-3/erlang-ale $ make we need to re-compile bits of pihwm here because NIFs require -fPICgcc -Lpriv -L/usr/lib/erlang/usr/lib -L/usr/lib/erlang/lib/erl_interface-3.7.17/lib -I/usr/local/include -I/usr/lib/erlang/lib/erl_interface-3.7.17/include -I/usr/lib/erlang/usr/include/ -Ideps/erlang_portutil -Ideps/pihwm/lib -o priv/pwm_nif.so -fPIC -shared |
hello Josh, I have a good news. I tried to make the erlang-ale once again, I got the same faults what I got before, but, I tried start an erlang shell (make shell) and just turn ON/OFF GPIO17. And it is working, the LED I plugged on that pin started to work :-) Now I'm interesting about meck and pihwm compilation error. Are these critical or ? many thanks for your grate support and helping me. |
hello,
Today I have started to learn and play with Erlang on Rasperry Pi B 1G RAM (http://www.raspberrypi.org/products/raspberry-pi-2-model-b/).
I have installed the latest erlang-mini, than I cloned the Erlang-ALE project from GitHub. I followed the instruction to compile the project. Unfortunately there are few errors when compile meck application what is one of the deps. project of Erlang-ALE.
I could fix it on my local copy, but for same reason I cannot able to push the changes in the git repo. See details below. I would be happy if someone could push the fix :-)
Log on the error
pi@raspberrypi ~/ethrbh/temp/erlang-ale $ make all
make[1]: Entering directory '/home/pi/ethrbh/temp/erlang-ale/deps/gproc'
./rebar get-deps
==> gproc (get-deps)
./rebar compile
==> gproc (compile)
make[1]: Leaving directory '/home/pi/ethrbh/temp/erlang-ale/deps/gproc'
make[1]: Entering directory '/home/pi/ethrbh/temp/erlang-ale/deps/meck'
/bin/sh: 1: ./rebar: not found
/bin/sh: 1: compile: not found
Makefile:6: recipe for target 'compile' failed
make[1]: *** [compile] Error 127
make[1]: Leaving directory '/home/pi/ethrbh/temp/erlang-ale/deps/meck'
make[1]: Entering directory '/home/pi/ethrbh/temp/erlang-ale/deps/pihwm'
OS on raspberry pi:
pi@raspberrypi ~/ethrbh/temp/erlang-ale $ uname -a
Linux raspberrypi 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l GNU/Linux
Solution what is working (for me at least)
Use the master branch of meck when clone in the erlang_ale/Makefile
old line:
dep_meck = https://github.com/eproxus/meck.git 0.7.2
new line:
dep_meck = https://github.com/eproxus/meck.git master
thanks for your help,
/Robi
The text was updated successfully, but these errors were encountered: