Custom Query (1030 matches)
Results (379 - 381 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1362 | fixed | Compiler bug on ARM32 during ARM::INSERT-SHIFTER-CONSTANT | ||
| Description |
see <https://lists.clozure.com/pipermail/openmcl-devel/2016-May/011274.html> |
|||
| #1363 | fixed | The license should be more visible | ||
| Description |
When looking at the CCL documentation and other information online it is not easy (well: it was not easy for me) to know what the license is. Checking out one of the platform-dependent versions from SVN also doesn't yield an obvious license in the root directory of the checkout. This is clearly not a vast problem -- I could always ask -- but it would be good if it was easy to find (I've never worried before but I'm thinking of developing an application with CCL which will get shipped to people who will care). It may be that I'm just being stupid and there is an obvious pointer to the license: in which case close this and laugh at me. |
|||
| #1367 | wontfix | Bring back armv6 | ||
| Description |
If I locally revert the change that disabled armv6 support in lisp-kernel/linuxarm, it still appears to work. (I haven’t tried the test suite at all though.) Since there are tons of original Raspberry Pi devices out there that are armv6, it might be worthwhile to keep armv6 running. For one thing, it might be easier to use for people who want to do GPIO stuff from Lisp; while I was doing it on an Intel Edison, not a Raspberry Pi, I could never make my Lisp bridge to libmraa actually work under SBCL, whereas it just worked immediately under CCL. |
|||
