Re: cannot open heap

Gary Byers said:
>
>
> On Mon, 29 Jul 2002, Serguei Panskikh wrote:
>
>> Hi,
>>
>> I've just downloaded OpenMCL 0.12.1 and tried to build it from the
>> source code (with separately downowaded interfaces). It builds. But it
>> doesn't run: # ./ppccl
>> Couldn't load lisp heap image from ./PPCCL
>> # ./ppccl PPCCL
>> Couldn't load lisp heap image from ./PPCCL
>> # ./ppccl ./PPCCL
>> Couldn't load lisp heap image from ./PPCCL
>> # ./ppccl ppc-image
>> Couldn't load lisp heap image from ./PPCCL
>
> The message isn't as informative as it could be: you get the same
> response (from the function "load_image() in ccl/lisp-kernel/pef.c) if
> the image file:
>  (a) doesn't exist
>  (b) doesn't contain a valid header
>  (c) something catastrophic happens when trying to load the image
>      (via the call to load_PEF_image()).
>
> I suppose that the first thing that we should try to do is to
> eliminate (a): does a file named PPCCL exist in the same directory as
> the kernel ?
>
> Before even approaching (b) or (c), I'd want to know why the kernel
> seems to be ignoring the argument you're giving it.  "./PPCCL" is
> the default image name if the kernel's invoked as "./ppccl" - it's just
> argv[0], case-inverted - but you're providing arguments in the last
> three examples above, and they seem to be getting ignored.
>
> Before getting to this stage, you would have had to build a
> bootstrapping image and to have invoked it as:
>
> # ./ppccl ppc-boot
>
> and I assume that worked.  Something isn't right here.

the image is not there. The last successful step was the build of binary
code of the kernel. Than I've tried to build the image using commands above
and it did not work. I might use wrong commands to build the image but that
was the only about kernel invocation I found in the documentation.

Once again, neither ./ppccl nor ./openmcl work being called without
arguments from appropriated directories, they return the same error message:
"Couldn't load lisp heap image from ./PPCCL"


>
>>
>> I guess I've followed the way described in the avaliable
>> documentation, but ... I understand that I may have done something
>> wrong. Or my OS (YDL 2.1) might be wrong. But as I followed the
>> documented procedure then it's certainly a bug of documentation. Or of
>> distribution - there is no ./configure file, is it?
>>
>
> There isn't a "configure" file: OpenMCL currently runs on one
> architecture and two platforms, and (so far) there isn't a whole lot to
> configure.

Good, then the problem is not with my system.

>
>> Anyway, how to build it? I've checked a binary distro of OpenMCL - it
>> works (it runs), but it doesn't help me - we have a policy - every
>> open source software must be build from sources before using it. Isn't
>> it open source?
>>
>
> Everything distributed with OpenMCL can be built from the sources
> provided.

Very good. Then I'll try to succeed with you help, right?

P.S. One authour of another open source project answered me: "Why would you
want ot build it from sources? Just download pre-build binaries and enjoy!"
That doesn't work. But that might be offtopic here.

>
> I believe that the procedure for doing so is fairly simple and fairly
> clearly documented, though I suppose that I'm not an objective judge of
> either of those issues.  I have no motivation for intentionally making
> the process complicated or making the documentation obscure, and if I'm
> doing either or both of those things unintentionally I'd certainly want
> to know.

I believe you. I just mean that if it is not a bug in my system, then it
might be either bug in software or in documentation or I do something wrong.

>
>
>>
>> Please help,
>
> I assume (perhaps incorrectly) that you've:
>
> a) rebuilt the kernel from source via "cd lisp-kernel/linux; make"

yes.

> b)generated a bootstrapping image ("ppc-boot") from the level-0 sources
>   via (XLOAD-LEVEL-0).

No. That is exactly a point I stuck - I cannot generate a bootstrapping
image as the kernel doesn't want to start without image.

> c) recompiled the lisp sources via (COMPILE-CCL)
> d) built a "full" image by:
> # ./ppccl ppc-boot
>   and saving an image via (SAVE-APPLICATION "PPCCL")
> e) are now at a stage where the kernel apparently ignores whatever
>   arguments you give it and complains that it can't load "./PPCCL".
>
> Like I said above, it's a little hard to understand how the kernel
> could have understood the argument provided in step (d) and then
> gone comatose in step (e); before exploring that, could you let me know
> whether or not these assumptions are correct ?

I think I should solve (b) at first.

-- 
Best Regards,
Serguei Panskikh



-----------------------------------------
   "Webmail by SquirrelMail!"
http://squirrelmail.org/