| Author |
Message |
|
| kruegger at operamail.com |
 Posted: Tue Apr 13, 1999 5:23 am |
 |
|
|
Guest
|
I managed to compile erlang successfully on Unixware 2.1.3 but when i type
'erl' to boot erlang, my erlang just crashed with following message :
{'init terminating in do_boot',{'can not load',erlang.get_file}}
init terminating in do_boot()
does anybody know about this error?
i must port erlang on unixware 2.1.3 because it is our development platform!
i attached erlang crash dump file together
Post generated using Mail2Forum (http://m2f.sourceforge.net) |
|
|
| Back to top |
|
| ulf.wiger at etxb.ericsso |
| Posted: Tue Apr 13, 1999 7:43 am |
|
|
|
Guest
|
Yes, this means that erlang cannot load one of the .jam files it needs
to get things going.
You can tell from the crash dump that the modules 'init' and
'erl_prim_loader' have been loaded, so I guess 'erlang' is next. You can
see how erlang loads the modules in the start script. From the crash
dump, I can't tell which one you're using, but this early in the start
phase there shouldn't be much difference.
The start scripts can be found under $ERL_ROOT/releases/<Vsn>/.
You're probably using start_clean or start. You'll find two files of
each - e.g. start.script and start.boot. The .script file is in parsable
ASCII format, and starts something like this:
[{preLoaded,[init,erl_prim_loader]},
{progress,preloaded},
{path,["$ROOT/lib/kernel-2.1.4/ebin","$ROOT/lib/stdlib-1.5.2/ebin"]},
{primLoad,[erlang,error_handler]},
{kernel_load_completed},
{progress,kernel_load_completed},
As an aside, the .script and .boot files are basically generated like:
Script = make_script(...),
{ok,Fd} = file:open("start.script", [write]),
io:format(Fd, "%% script generated at ~p ~p~n~p.~n", [Script]),
file:close(Fd),
file:write_file("start.boot", term_to_binary(Script)).
If you want to see in more detail what's happening during the boot
phase, you can start erlang with the -init_debug flag.
/Uffe
Freddie Kruegger wrote:
>
> I managed to compile erlang successfully on Unixware 2.1.3 but when i type
> 'erl' to boot erlang, my erlang just crashed with following message :
>
> {'init terminating in do_boot',{'can not load',erlang.get_file}}
> init terminating in do_boot()
>
> does anybody know about this error?
> i must port erlang on unixware 2.1.3 because it is our development platform!
>
> i attached erlang crash dump file together
>
> ------------------------------------------------------------------------
>
> Name: erl_crash.dump
> erl_crash.dump Type: unspecified type (application/octet-stream)
> Encoding: 7bit
--
Ulf Wiger, Chief Designer AXD 301 <ulf.wiger_at_etxb.ericsson.se>
Ericsson Telecom AB tfn: +46 8 719 81 95
Varuv |
|
|
| Back to top |
|
| kruegger at operamail.com |
| Posted: Tue Apr 13, 1999 11:16 am |
|
|
|
Guest
|
hmm.
now erlang is running on Data General AViiON 2600 Unixware 2.1.3.
there was something wrong with installation. *.jam files were not installed
properly. it's strange...
Anyway, with slight modification on Makefile and sys.c, it seems working all
right.
While compiling, Makefile does not recognize /usr/ucblib and /usr/ucbinclude
directory... so i added to it.
In Unixware 2.1.3, we have to use fp.h instead of floatingpoint.h, which was
included by sys.c file.
By the way, when asn.1 compiler will support REAL type?
Now i am compiling rest of libraries...
i want to say thanks who helped me....
>Yes, this means that erlang cannot load one of the .jam files it needs
>to get things going.
>
>You can tell from the crash dump that the modules 'init' and
>'erl_prim_loader' have been loaded, so I guess 'erlang' is next. You can
>see how erlang loads the modules in the start script. From the crash
>dump, I can't tell which one you're using, but this early in the start
>phase there shouldn't be much difference.
>
>The start scripts can be found under $ERL_ROOT/releases/<Vsn>/.
>
>You're probably using start_clean or start. You'll find two files of
>each - e.g. start.script and start.boot. The .script file is in parsable
>ASCII format, and starts something like this:
>
> [{preLoaded,[init,erl_prim_loader]},
> {progress,preloaded},
>
>{path,["$ROOT/lib/kernel-2.1.4/ebin","$ROOT/lib/stdlib-1.5.2/ebin"]},
> {primLoad,[erlang,error_handler]},
> {kernel_load_completed},
> {progress,kernel_load_completed},
>
>
>As an aside, the .script and .boot files are basically generated like:
>
> Script = make_script(...),
> {ok,Fd} = file:open("start.script", [write]),
> io:format(Fd, "%% script generated at ~p ~p~n~p.~n", [Script]),
> file:close(Fd),
> file:write_file("start.boot", term_to_binary(Script)).
>
>
>If you want to see in more detail what's happening during the boot
>phase, you can start erlang with the -init_debug flag.
>
>/Uffe
Post generated using Mail2Forum (http://m2f.sourceforge.net) |
|
|
| 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
