<html><head/><body>I'm running CLISP 2.49 armhf version on Android Samsung Galaxy Note II, built natively against glibc 2.17.<br>
<br>
If I try to load cl+ssl it segfaults:<br>
<br>
[1]> (asdf:load-system 'cl+ssl)<br>
0 errors, 0 warnings<br>
;; Loading file /mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/cl+ssl.asd ...<br>
;; Loaded file /mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/cl+ssl.asd<br>
;; Compiling file /mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/package.lisp ...<br>
;; Wrote file /data/home/.cache/common-lisp/clisp-2.49-unix-armv7l/mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/p<br>
ackage-ASDF-TMP.fas <br>
;; Loading file /data/home/.cache/common-lisp/clisp-2.49-unix-armv7l/mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl<br>
/package.fas ... <br>
;; Loaded file /data/home/.cache/common-lisp/clisp-2.49-unix-armv7l/mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/<br>
package.fas <br>
;; Compiling file /mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/reload.lisp ...<br>
;; Wrote file /data/home/.cache/common-lisp/clisp-2.49-unix-armv7l/mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl/r<br>
eload-ASDF-TMP.fas <br>
;; Loading file /data/home/.cache/common-lisp/clisp-2.49-unix-armv7l/mnt/sdcard-ext/sdb4/lisp/cl-plus-ssl<br>
/reload.fas ... <br>
*** - handle_fault error2 ! address = 0x4eb0d218 not in [0x19c00000,0x1a6fe778) !<br>
SIGSEGV cannot be cured. Fault address = 0x4eb0d218.<br>
GC count: 792<br>
Space collected by GC: 0 954748196<br>
Run time: 134 180000<br>
Real time: 397 858696<br>
GC time: 19 335000<br>
Permanently allocated: 94080 bytes.<br>
Currently in use: 19118684 bytes.<br>
Free space: 22856 bytes.<br>
Segmentation fault <br>
<br>
I also run CLISP in an armel Ubuntu core chroot built natively there and cl+ssl loads no prob.<br>
<br>
Am gonna build an armhf CLISp version in an armh Ubuntu chroot to test if it's connected with architecture, however strange that it would load in armel and fail armhf, no? Ideas?<br>
--<br>
白い熊</body></html>