Hello,<br><br>While working on asmgcc-64, I ran into this issue. For some reason, PyPy wants to link libffi statically on some platforms, Linux included. But when compiling with the &quot;shared&quot; option (as is done in some asmgcroot tests), you get link errors like:<br>
<br>/usr/bin/ld: /usr/lib/libffi.a(ffi64.o): relocation R_X86_64_32S against `.rodata&#39; can not be used when making a shared object; recompile with -fPIC<br>/usr/lib/libffi.a: could not read symbols: Bad value<br><br>I interpret this to mean that since we building a shared library, the resulting library must be position independent, so we can&#39;t link in non-PIC such as is found in the static version of libffi on my system. (Ubuntu 10.04, x86-64). And indeed, if I switch to linking dynamically, the error goes away and things seem to work.<br>
<br>However, I don&#39;t want to just blindly enable dynamic linking, because there must be a reason it was configured to link statically in the first place. What is that reason?<br><br>Also, what steps should I take here? I think I need to enable dynamic linking of libffi on x86-64 Linux when building a shared library at the very least, but to reduce the number of code paths, I&#39;m somewhat inclined to link dynamically whether we&#39;re building a library or not. What do you guys think?<br>
<br>Thanks,<br><br>Jason<br>