From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Lisp is not Lisp is... ?
Date: Wed, 18 Mar 2015 17:31:51 +0000 (UTC) [thread overview]
Message-ID: <loom.20150318T182117-520@post.gmane.org> (raw)
In-Reply-To: 20150316034209.GA4154@solfire
<Meino.Cramer <at> gmx.de> writes:
> Then I installed dev-lisp/gcl there (which compiles fine).
You might want to cross-compile the codes and dependent codes
on a x86 machine and move them over, as another test....
I'd first try by only setting the minimum you need to get
the codes to compile. Then test and see if they work on the
arm(target) as you expect with some know valid lisp codes.
On SoC often operands are said to be supported, but it's in
software only and that causes severe to critical timing problems
when desired codes are actually run on the target.
Find a working lisp for a common/similar arm chip, like R. pi?
good-hunting,
James
prev parent reply other threads:[~2015-03-18 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 3:42 [gentoo-user] Lisp is not Lisp is... ? Meino.Cramer
2015-03-16 7:04 ` R0b0t1
2015-03-18 17:31 ` James [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20150318T182117-520@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox