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
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,
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.
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':
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'
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'
