Re: fontforge breakage
Hi,
On Mon, Mar 09, 2009 at 10:36:09AM +, Edd Barrett wrote:
Is fontforge already installed? If so, could you try to pkg_delete it
before building the new version?
It's not installed at the moment.
I also tried adding 'LDFLAGS = -lutil', no joy.
It fails iff there's a symlink python - python2.5 in /usr/local/bin.
You have such a symlink, I usually don't (but I just tried with it,
after I noticed that configure looks for python).
NB: this is *one* reason I think tools like autoconf create more
problems than they attempt to solve.
I'll change the port so that it
a) always detects ${MODPY_BIN} at configure time and uses it at build
time,
b) doesn't fail when linked.
Ciao,
Kili
Re: fontforge breakage
On Mon, Mar 09, 2009 at 09:10:28PM +0100, Matthias Kilian wrote:
I'll change the port so that it
a) always detects ${MODPY_BIN} at configure time and uses it at build
time,
b) doesn't fail when linked.
HORRIBLE PATCH ALERT!
Please test. I could need some hints from the python gurus, especially
about the python${MODPY_VERSION}-config hack -- how is python2.5-config
supposed to be used at all together with python.port.mk?
I've also an update to a newer version of fontforge, but I want to
get this fix in first.
Ciao,
Kili
Index: Makefile
===
RCS file: /cvs/ports/print/fontforge/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- Makefile27 Oct 2008 17:58:52 - 1.12
+++ Makefile9 Mar 2009 21:01:56 -
@@ -5,7 +5,7 @@ SHARED_ONLY=Yes
COMMENT= vector font editor/converter
DISTNAME= fontforge_full-20080927
-PKGNAME= ${DISTNAME:S,_full,,}
+PKGNAME= ${DISTNAME:S,_full,,}p0
EXTRACT_SUFX= .tar.bz2
SHARED_LIBS= fontforge 1.0 \
gdraw 3.0 \
@@ -28,15 +28,17 @@ PERMIT_DISTFILES_CDROM= Yes
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=fontforge/}
WANTLIB= ICE SM X11 Xau Xdmcp Xext Xi c freetype m \
- pthread xkbfile xkbui z
+ pthread util xkbfile xkbui z
MODULES= devel/gettext lang/python
+MODPY_VERSION= 2.5
LIB_DEPENDS= png.=5::graphics/png \
tiff.=38::graphics/tiff\
ungif.=5::graphics/libungif\
jpeg.=62::graphics/jpeg\
- xml2.=9::textproc/libxml
+ xml2.=9::textproc/libxml \
+ ${MODPY_LIB_DEPENDS}
WRKDIST= ${WRKDIR}/${DISTNAME:S,_full,,}
@@ -46,7 +48,10 @@ CONFIGURE_ENV= CPPFLAGS=-I${LOCALBASE}
-I${LOCALBASE}/include/libpng\
LDFLAGS=-L${X11BASE}/lib -L${LOCALBASE}/lib\
-lintl -liconv -lz
-CONFIGURE_ARGS=--with-regular-link --without-freetype-src
+CONFIGURE_ARGS=--without-freetype-src \
+ --with-python=${MODPY_BIN} \
+ --with-python-lib=$$(python${MODPY_VERSION}-config
--libs) \
+ --with-regular-link
USE_GMAKE= Yes
USE_LIBTOOL= Yes
USE_X11= Yes
Re: fontforge breakage
Hi Kili-
On Mon, Mar 09, 2009 at 10:16:17PM +0100, Matthias Kilian wrote:
On Mon, Mar 09, 2009 at 09:10:28PM +0100, Matthias Kilian wrote:
I'll change the port so that it
a) always detects ${MODPY_BIN} at configure time and uses it at build
time,
b) doesn't fail when linked.
HORRIBLE PATCH ALERT!
Please test. I could need some hints from the python gurus, especially
about the python${MODPY_VERSION}-config hack -- how is python2.5-config
supposed to be used at all together with python.port.mk?
Untested, but what you sent looks right. Honestly, I've never used
python*-config and I don't believe python.port.mk has any special
stuff for it. I wouldn't be opposed to adding MODPY_CONFIG to
python.port.mk to make things simpler, either.
Thanks!
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | email.willma...@ml1.net |
*-[ BSD: Live Free or Die ]*
fontforge breakage
Hi, Fontforge appears to be broken in -current: /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c3a): In function `posix_openpty': : undefined reference to `openpty' /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c8e): In function `posix_forkpty': : undefined reference to `forkpty' collect2: ld returned 1 exit status gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/w-fontforge-20080927/fon tforge-20080927/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 I have checked that both the fontforge and python ports are up to date. I am using a 2 week(ish) old snapshot on i386. Thanks -- Best Regards Edd Barrett (Freelance software developer / technical writer / open-source developer) http://students.dec.bmth.ac.uk/ebarrett
Re: fontforge breakage
On Sun, Mar 8, 2009 at 11:22 AM, Edd Barrett vex...@gmail.com wrote: Hi, Fontforge appears to be broken in -current: /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c3a): In function `posix_openpty': : undefined reference to `openpty' /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c8e): In function `posix_forkpty': : undefined reference to `forkpty' collect2: ld returned 1 exit status gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/w-fontforge-20080927/fon tforge-20080927/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 I have checked that both the fontforge and python ports are up to date. I am using a 2 week(ish) old snapshot on i386. Make sure you are linking with -lutil. That may be your problem. --patrick
Re: fontforge breakage
On Sun, Mar 08, 2009 at 07:22:48PM +, Edd Barrett wrote: Fontforge appears to be broken in -current: /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c3a): In function `posix_openpty': : undefined reference to `openpty' /usr/local/lib/python2.5/config/libpython2.5.a(posixmodule.o)(.text+0x1c8e): In function `posix_forkpty': : undefined reference to `forkpty' collect2: ld returned 1 exit status gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/w-fontforge-20080927/fon tforge-20080927/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 I have checked that both the fontforge and python ports are up to date. Is fontforge already installed? If so, could you try to pkg_delete it before building the new version? Ciao, Kili
