Question about "shlib-with-non-pic-code", possibly caused by assembler code?

[Roland McGrath]

It does require some knowledge of the particular machine you're dealing
with.  You can look at the .o files that go into the .so with objdump -rd
and look for the non-PIC relocations they use.  If you don't know how to
identify those already, then you will probably have a hard time adjusting
the assembly code.