Bug#605871: [Pkg-fonts-devel] Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Fabian Greffrath
Am Montag, den 15.04.2013, 15:44 +0900 schrieb Hideki Yamane: --with-freetype-src option should be used with relevant path like --with-freetype-src=/foobar. But anyway, freetype source file is necessary to include to build with --with-freetype-bytecode option. If this configure options is

Bug#605871: [Pkg-fonts-devel] Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Paul Wise
On Mon, Apr 15, 2013 at 2:44 PM, Hideki Yamane wrote: --with-freetype-src option should be used with relevant path like --with-freetype-src=/foobar. But anyway, freetype source file is necessary to include to build with --with-freetype-bytecode option. If not, configure script warns for

Bug#605871: [Pkg-fonts-devel] Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Hideki Yamane
On Mon, 15 Apr 2013 09:16:12 +0200 Fabian Greffrath fab...@greffrath.com wrote: If this configure options is only relevant for building the bundled freetype copy, then it should be alright as it currently is. The freetype system library in Debian already has the byte-code interpreter enabled.

Bug#605871: [Pkg-fonts-devel] Bug#605871: fontforge runs find / during the configure step

2010-12-04 Thread Nicolas Spalinger
On 04/12/10 09:30, Matthias Klose wrote: Package: fontforge Version: 0.0.20100501-3 checking trying to find the freetype source directory -- be patient... runs ... find / -name ttobjs.h -print for several hours, including network shares. Is this serious? AFAICT the

Bug#605871: [Pkg-fonts-devel] Bug#605871: fontforge runs find / during the configure step

2010-12-04 Thread Kęstutis Bilūnas
Št, 2010 12 04 10:30 +0100, Matthias Klose rašė: Package: fontforge Version: 0.0.20100501-3 checking trying to find the freetype source directory -- be patient... runs ... find / -name ttobjs.h -print for several hours, including network shares. Is this serious? An option in