From owner-freebsd-ports@FreeBSD.ORG Tue Oct 30 13:15:06 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7329216A419 for ; Tue, 30 Oct 2007 13:15:06 +0000 (UTC) (envelope-from cyberbotx@cyberbotx.com) Received: from alnrmhc16.comcast.net (alnrmhc16.comcast.net [204.127.225.96]) by mx1.freebsd.org (Postfix) with ESMTP id 4138913C4E8 for ; Tue, 30 Oct 2007 13:15:05 +0000 (UTC) (envelope-from cyberbotx@cyberbotx.com) Received: from kirby.cyberbotx.com ([68.62.97.217]) by comcast.net (alnrmhc16) with ESMTP id <20071030131504b16008br0ve>; Tue, 30 Oct 2007 13:15:05 +0000 Message-ID: <47272E58.2050607@cyberbotx.com> Date: Tue, 30 Oct 2007 09:15:04 -0400 From: Naram Qashat User-Agent: Thunderbird 2.0.0.6 (X11/20071007) MIME-Version: 1.0 To: Andriy Gapon References: <4725BBE0.3000605@icyb.net.ua> <4725DB69.5000800@cyberbotx.com> <4725DC45.7080509@icyb.net.ua> <47263D48.7030001@cyberbotx.com> <4726E44E.3090100@icyb.net.ua> In-Reply-To: <4726E44E.3090100@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: print/fontforge: link failure on amd64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 13:15:06 -0000 I'll add in an option to enable or disable Python support, then, and mark the port broken when Python is enabled on amd64. Naram Qashat Andriy Gapon wrote: > on 29/10/2007 22:06 Naram Qashat said the following: >> I'm using FreeBSD 6.2 on i386 and it links Python just fine with >> /usr/local/lib/python2.5/config/libpython2.5.a, so I suspect it has something to >> do with how Python gets built on an amd64. I don't have one to test it on, but >> have you tried rebuilding Python and then Fontforge? I just want to see if it's >> Python's fault, Fontforge's fault, or something weird with the way Fontforge's >> libtool is handling Python. I'm not even sure if Python is actually used by >> Fontforge either. I haven't looked into that. > > Yes, I did rebuild python before fontforge. > I think that this indeed has something to do with amd64. > >> Andriy Gapon wrote: >>> 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/libpython2.5.so 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 ../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. >>>>> > >