[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft] Problems about ftdmo29

From: Werner LEMBERG
Subject: Re: [ft] Problems about ftdmo29
Date: Wed, 18 Apr 2018 09:28:27 +0200 (CEST)

> objs\ftdump.o:ftdump.c:(.text+0xc99): undefined reference to 
> `put_unicode_be16'
> objs\ftdump.o:ftdump.c:(.text+0xd1b): undefined reference to `put_ascii'
> objs\ftdump.o:ftdump.c:(.text+0xd89): undefined reference to `put_ascii'
> objs\ftdump.o:ftdump.c:(.text+0xda9): undefined reference to 
> `put_unicode_be16'
> objs\ftdump.o:ftdump.c:(.text+0xe39): undefined reference to 
> `put_unicode_be16'
> objs\ftdump.o:ftdump.c:(.text+0x14d3): undefined reference to `put_ascii'
> objs\ftdump.o:ftdump.c:(.text+0x14f6): undefined reference to 
> `put_unicode_be16'

I can repeat that.  However, I don't have enough time (and,
admittedly, not enough interest) to fix that.  Maybe there are some
Jam users who want to improve that.

I applied some minor fixes to the jam build system.  Using the current
git, it works for me if I first call `jam' in the `freetype2'
directory, then followed by calling `jam' again in the
`freetype2-demos' program.

Please check.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]