Op 19-aug-2011, om 22:34 heeft Ken Moffat het volgende geschreven:
> On 18/08/2011, Pol Vangheluwe <[email protected]> wrote:
>> Op 17-aug-2011, om 13:20 heeft Andrew Benton het volgende geschreven:
>>>
>>> So why is it just you getting this error?
>>>
>>> Andy
Well, that's a good question…
Am I really the only one facing this problem?
After a lot of trial-and-error without any progress, I gave up and built
ghostscript with the built-in version of Freetype.
This build was successful and I compared both Makefiles. There is only one
difference.
When I build against the external FreeType library:
FT_BRIDGE=1
SHARE_FT=1
FTSRCDIR=
FT_CFLAGS= -DUSE_LIBPAPER -I/usr/include/freetype2
FT_LIBS=-lfreetype
I don't see anything wrong here. BTW: I also built libpaper to avoid a
configuration warning - is not mentioned in BFLS.
When I build with the internal FreeType source:
FT_BRIDGE=1
SHARE_FT=0
FTSRCDIR=freetype
FT_CFLAGS=-Ifreetype/include
FT_LIBS=
So, I think thet Ghostscript is not creating an internal library, but is
immediately linking the object files.
Could it be that the FreeType bridge (fapi_ft.c) is simply not configured to
link with an external library?
pvg
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
