Yes, libffi is not build with -fPIC, for reasons unknown to me. This is a known debian bug. You can instead enable dynamic linking with libffi, which will make your binary less movable between various linux distros (but maybe you don't care)
On Tue, Sep 11, 2012 at 11:41 AM, Max Lavrenov <max.lavre...@gmail.com> wrote: > Hello > > When i tried build master pypy with --shared flag i got error: > > [translation:ERROR] /usr/bin/ld: /usr/lib/libffi.a(ffi64.o): relocation > R_X86_64_32S against `.rodata' can not be used when making a shared object; > recompile with -fPIC > [translation:ERROR] /usr/lib/libffi.a: could not read symbols: Bad value > [translation:ERROR] collect2: ошибка: выполнение ld завершилось с кодом > возврата 1 > [translation:ERROR] make: *** [libpypy-c.so] Ошибка 1 > [translation:ERROR] """) > > What that means? Should i rebuild my libffi package with -fPIC? Right now > i've temporary fixed this probleb with patch def find_libffi_a(): function > so it always use dynamic linking. > Will it cause "endless troubles for installing" ( according comment from > clibffi.py ) ? > > Thanks. > > Best regards, > Max > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
