|
|
| Author |
Message |
< Erlang ~ {error,nofile} on andLinux |
| vim |
 Posted: Wed Oct 01, 2008 8:07 am |
 |
|
|
User
Joined: 01 Oct 2008
Posts: 19
|
Hi i am trying to run erlang on andLinux, i have installed andLinux and it actually provide you a way to run an linux/ubuntu os in parallel to my windows os. i don't know much about the details of how it works, but it gives me a terminal and i can even apt-get distributions and install them. so after little playing around, i have installed erlang and invoked 'erl', i got the erlang shell and basic things actually work fine, the problem is i get {error,nofile} on compilation of files. from what i see the beam file is created, so the compilation works, and from the error message i understand the 'loading' of the beam doesn't succeed.
look at the shell output:
Code:
$ erl
Erlang (BEAM) emulator version 5.5.5 [source] [async-threads:0] [kernel-poll:false]
Eshell V5.5.5 (abort with ^G)
1> ls().
fact.erl
ok
2> c(fact).
{error,nofile}
3> ls().
fact.beam fact.erl
ok
4>
i know this topic is strange: andLinux and erlnag, but i don't know how even to start and debug it...
do you have any suggestions? |
|
|
| Back to top |
 
|
| Mazen |
| Posted: Wed Oct 01, 2008 11:49 am |
|
|
|
User
Joined: 20 Jul 2006
Posts: 164
Location: London
|
Hmm... interesting... I don't know anything about andLinux but I guess the problem might have something to do with how paths are resolved and translated to windows paths...
anyway, I would suggest to start here:
http://www.erlang.org/doc/man/code.html
Hope this gets you started atleast 
/Mazen
PS: I would recommend you to run a virtual machine if you want to use Linux in windows... Try VMware ... |
|
|
| Back to top |
|
| vim |
| Posted: Wed Oct 01, 2008 2:46 pm |
|
|
|
User
Joined: 01 Oct 2008
Posts: 19
|
after i read what you wrote itried coping the beam to erlang installation folder, and it worked. so i thought, what the heck and i went back to my local folder, and just tried to ignore this message and to invoke the app... well, it works... 
Code:
$ rm fact.beam
$ erl
Eshell V5.5.5 (abort with ^G)
1> c(fact).
{error,nofile}
2> fact:fac(5).
120
3> fact:mult(5,5).
25
4>
so, i am still with this funny message, though i'll try to dig into it in the documentation, as you suggested.
btw, i tried vmware and virtualbox and both are very mature solutions. i also tried cygwin. but andLinux is something else, it is actually runs in parallel and it is like opening a terminal shell on your windows, since it maps any win folder into it's own, but i guess this is not the place to discuss about it
anyway i'll keep digging, if anyone have more suggestions i will be glad to hear about it.
cheers! |
|
|
| Back to top |
|
| uwiger |
| Posted: Sat Nov 01, 2008 3:21 pm |
|
|
|
User
Joined: 03 Jul 2006
Posts: 604
Location: Sweden
|
vim wrote: the problem is i get {error,nofile} on compilation of files. from what i see the beam file is created, so the compilation works, and from the error message i understand the 'loading' of the beam doesn't succeed.
I've seen the same problem, but only when working against a windows file system mounted using cofs.
When I work against a "normal" file system (that is, a file system image mounted using cobd), things have worked perfectly so far. |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
