[Ecls-list] Trying to compile ecl on armel (round 2)
Elliott Slaughter
elliottslaughter at gmail.com
Thu Aug 20 05:39:40 UTC 2009
On Tue, Aug 18, 2009 at 6:09 AM, Juan Jose Garcia-Ripoll <
juanjose.garciaripoll at googlemail.com> wrote:
> On Mon, Aug 17, 2009 at 2:08 AM, Elliott
> Slaughter<elliottslaughter at gmail.com> wrote:
> > I am using the Maemo SDK+ 1.0.0 [1] from Nokia. The SDK includes the
> cross
> > compiler [2], the emulator (qemu), etc, the versions of which are all
> > determined by the rootstrap (I'm using the last version for diablo [3]).
> > Hope this helps.
>
> I have been working for two days with the maemo-sdk v4.1.
>
> For some reason the garbage collector fails to work on it. Trying a
> newer version of the garbage collector also does not seem to help. But
> as I said, it is a problem with the Boehm-Weiser garbage collection
> library: it generates SIGSEGV signals without apparent reason.
>
> Unfortunately the maemo environment is deficient enough that debugging
> is not possible (I had to use printfs everywhere to find the problem)
> and it is currently out of my reach to find out the actual problem
> with that library.
>
> From what I can say, this is not arm-specific, for the same library
> works in other ARM emulator images, with probably newer versions of
> qemu -- it is difficult for me to find out the version used by
> scratchbox here, but it seems to be lacking a lot of system calls.
>
I have been trying CPU transparency mode (
http://maemo-sdk.garage.maemo.org/cpu-transparency-guide.html), which gets
me significantly further in the build process. (Basically, it set up an sshd
process on the device and copy binaries files over so they can run natively
instead of emulating them.)
When running natively, I can load the minimal lisp image and start
compiling... Unfortunately, the process is a bit finicky and I keep getting
errors like the following if I let the device sleep too long.
;;; Internal error: Read or write operation to stream #<output stream
#P"build:lsp;predlib.h.NEWEST"> signaled an error.
;;; Explanation: Transport endpoint is not connected.
;;; Internal error: Cannot close stream #<output stream
#P"build:lsp;predlib.h.NEWEST">.
;;; Explanation: Transport endpoint is not connected.
;;; Internal error: Read or write operation to stream #<output stream
#P"build:lsp;predlib.c.NEWEST"> signaled an error.
;;; Explanation: Transport endpoint is not connected.
(compile-file "src:lsp;seq.lsp" :output-file #P"build:lsp;seq.o.NEWEST"
:SYSTEM-P T :C-FILE T :DATA-FILE T :H-FILE T)
Filesystem error with pathname "src:lsp;seq.lsp".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
--
Elliott Slaughter
"Don't worry about what anybody else is going to do. The best way to predict
the future is to invent it." - Alan Kay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20090819/d344566c/attachment.html>
More information about the ecl-devel
mailing list