print/fontforge: link failure on amd64

Andriy Gapon avg at icyb.net.ua
Mon Oct 29 12:27:56 PDT 2007


I have the following problem while building print/fontforge version
20071002 on FreeBSD 6.2-RELEASE-p6 amd64:
*** Warning: Linking the shared library ../libfontforge.la 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/libintl.so  -march=athlon64 -Wl,-soname
-Wl,libfontforge.so.1 -o ../.libs/libfontforge.so.1
/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]: *** [../libfontforge.la] 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