Hi Alex,

I am trying to compile the latest picolisp 3.1.10 on 32 bit ARM.

I remember I sent a patch fixing ARM compilation a while ago but that
wasn't accepted, because the aditional cases would make the Makefile

I ca fix it quickly simply by calling

   (cd src ; sed -i s/-m32//g Makefile)

but then I get another error which I don't remember seeing before:

   gcc -o ../lib/ext -shared -export-dynamic ext.o  -lcrypt
   ext.o: relocation R_ARM_MOVW_ABS_NC against `Nil' can not be used when
   making a shared object; recomp\ile with -fPIC
   ext.o: could not read symbols: Bad value
   collect2: error: ld returned 1 exit status
   Makefile:151: recipe for target '../lib/ext' failed
   make: *** [../lib/ext] Error 1

So my questions:

1) is it ok to simply compile everything with -fPIC?  E.g. fixing the
   makefile by calling

   (cd src ; sed -i s/-m32/-fPIC/g Makefile)

   or the picolisp binary should not be compiled with -fPIC?

2) How do I run the picolisp test suite to verify, that the build is

Thanks a lot,

UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to