Date: Mon, 29 Oct 2007 09:08:57 -0400 From: Naram Qashat <cyberbotx@cyberbotx.com> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-ports@freebsd.org Subject: Re: print/fontforge: link failure on amd64 Message-ID: <4725DB69.5000800@cyberbotx.com> In-Reply-To: <4725BBE0.3000605@icyb.net.ua> References: <4725BBE0.3000605@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Naram Qashat 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 ../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. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4725DB69.5000800>