When running         etc/make-liarc.sh 
it ends with:

initialize: .....
initialize: ....
initialize: (runtime floating-point-environment)
broken heart in scan: 0x88625093
scan = 0x75141038; to = 0x751410f0
Inconsistency detected within critical section "garbage collector".
* Error in `../microcode/scheme': double free or corruption (out): 0x7509e008 *

My suspicion is that the patches once applied to microcode/confshared.h
for the ARM processor architecture regarding floating point do ONLY work
for older Raspberry Pi machines. 

Other files involved may be
microcode/floenv.c
microcode/gcloop.c
runtime/floenc.scm

More details about the symptoms are here:------------------------------------------------

The commans that does not run actually is

 ../microcode/scheme --library ../lib --fasl http://www.gnu.org/software/mit-scheme/lib/runtime/make.so --heap 6000 --batch-mode

http://www.gnu.org/software/mit-scheme/lib/runtime/packag.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/gcdemn.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/gc.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/boot.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/queue.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/equals.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/list.so initialized evaluated
http://www.gnu.org/software/mit-scheme/lib/runtime/symbol.so initialized evaluated
...
...
...
initialize: (runtime regular-sexpression) [initialize-conditions!]
initialize: (runtime os-primitives) [initialize-system-primitives!]
initialize: (runtime floating-point-environment)
broken heart in scan: 0x88625093
scan = 0x75208038; to = 0x752080f0

Inconsistency detected within critical section "garbage collector".
* Error in `../microcode/scheme': double free or corruption (out): 0x75165008 *

>> A system software fault has occurred within critical section "garbage collector".
>> [signal 6 (SIGIOT), code -6]
>> The stack has overflowed overwriting adjacent memory.
>> This was probably caused by a runaway recursion.
>> Successful recovery is unlikely.

Choose one of the following actions:
  D = dump core
  I = terminate immediately
  N = terminate normally
  R = attempt recovery
  Q = terminate normally
Action ->