print/fontforge: link failure on amd64

Andriy Gapon avg at
Mon Oct 29 10:31:42 PDT 2007

on 29/10/2007 15:08 Naram Qashat said the following:
> I'm really not sure about it, but maybe Python needs rebuilding for that? 
> Either that or I could look into seeing if there's an option to enable/disable 
> Python support.  I think by default it just auto-detects if Python is there and 
> tries to use it if it is.

Just in case: there is already
/usr/local/lib/python2.5/config/ installed, I hacked
Makefile to link against it and everything seems to be OK.

> Andriy Gapon wrote:
>> I have the following problem while building print/fontforge version
>> 20071002 on FreeBSD 6.2-RELEASE-p6 amd64:
>> *** Warning: Linking the shared library ../ against the
>> *** static library /usr/local/lib/python2.5/config/libpython2.5.a is not
>> portable!
>> cc -shared  .libs/autohint.o .libs/autosave.o ...
>> /usr/local/lib/python2.5/config/libpython2.5.a -lutil -lpthread -lm
>> /usr/local/lib/  -march=athlon64 -Wl,-soname
>> -Wl, -o ../.libs/
>> /usr/bin/ld: /usr/local/lib/python2.5/config/libpython2.5.a(abstract.o):
>> relocation R_X86_64_32 can not be used when making a shared object;
>> recompile with -fPIC
>> /usr/local/lib/python2.5/config/libpython2.5.a: could not read symbols:
>> Bad value
>> gmake[1]: *** [../] Error 1
>> gmake[1]: Leaving directory
>> `/usr/ports/print/fontforge/work/fontforge-20071002/fontforge'
>> gmake: *** [fontforge] Error 2
>> *** Error code 2
>> Stop in /usr/ports/print/fontforge.
>> I think that there either should be a "PIC" version of libpython2.5.a
>> and that's what fontforge should link to or it should link to .so
>> version of the library.

Andriy Gapon

More information about the freebsd-ports mailing list