[erlang-questions] clueless newbie can't compile

John Chandler <>
Tue Jun 17 06:59:45 CEST 2008


I thank all who responded.  I reinstalled CEAN, and got this:
====
Eshell V5.5.5  (abort with ^G)
1> cean:install(compile).
compile was not installed. failed to find dependencies: no_pub_file
ok
2>
====

Which is better than what I had been getting before.  I see that I  
installed
the Production version, so I guess I'll scorch the earth here again  
and re-do
w/the Developer version.  Is that "no_pub_file" message interpretable?

I notice that the full release is in cean_base.tar.gz, (~3MB) whereas
the "cean library" is downloadable from the FAQ page in the file,
cean.tar.gz (113KB).  This smaller file appears to contain different
versions of each of the cean files, and some that do not appear in
cean_base.tar.gz.  Does anyone know if it is advisable to extract
the smaller file over the tree extracted from the larger file?  I would
default to "no," unless things still don't work.

-jmc

On Jun 16, 2008, at 11:13 AM, Kevin A. Smith wrote:

> I think CEAN also has (had?) a developer version of the install which
> had things like the compiler installed by default.
>
> --Kevin
> On Jun 16, 2008, at 2:04 AM, Bengt Kleberg wrote:
>
>> Greetings,
>>
>> CEAN does not include all of Erlang/OTP in the initial install. The
>> compiler is not present.
>> You should be able to do:
>>
>> cean:install(compile).
>>
>>
>> bengt
>>
>> On Mon, 2008-06-16 at 03:23 +0200, Robert Virding wrote:
>>> 2008/6/16 John Chandler <>:
>>>        I can't interpret the error message, either.
>>>
>>>        And then, within erl, to type "c(tut).".  Which also seems
>>>        fine.  What
>>>        happens is:
>>>
>>>        ====
>>>        1> c(tut).
>>>        ** exited:
>>>        {undef,[{compile,file,[tut,[report_errors,report_warnings]]},
>>>                           {c,c,2},
>>>                           {erl_eval,do_apply,5},
>>>                           {shell,exprs,6},
>>>                           {shell,eval_loop,3}]} **
>>>
>>>        =ERROR REPORT==== 15-Jun-2008::20:07:51 ===
>>>        Error in process <0.29.0> with exit value:
>>>        {undef,[{compile,file,[tut,
>>>        [report_errors,report_warnings]]},{c,c,2},{erl_eval,do_apply,
>>> 5},
>>>        {shell,exprs,6},{shell,eval_loop,3}]}
>>>
>>> Not being familiar with CEAN I don't really know why, but the error
>>> report indicates that the function compile:file/2 is undefined, the
>>> 'undef ' error. In this case this is caused by Erlang not being able
>>> to find the compile module as we know the file/2 function exists in
>>> the module.
>>>
>>> As I said I am not familiar with CEAN so I can't help you with *why*
>>> Erlang can't find the module.
>>>
>>> Robert
>>>
>>>
>>> _______________________________________________
>>> erlang-questions mailing list
>>> 
>>> http://www.erlang.org/mailman/listinfo/erlang-questions
>>
>> _______________________________________________
>> erlang-questions mailing list
>> 
>> http://www.erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://www.erlang.org/mailman/listinfo/erlang-questions

NOTICE: Due to Presidential Executive Orders, the National Security  
Agency may have read this email without warning, warrant, or notice.  
They may do  this without any judicial or legislative oversight. You  
have little recourse nor protection except to call for the  
impeachment of the current President.




More information about the erlang-questions mailing list