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

Re: [Pkg-fonts-devel] Bug#621932: fontforge: FTBFS: eval: 1: base_compile+= -c: not found


On Sat, 9 Apr 2011 14:26:06 +0200
Lucas Nussbaum <lucas@lucas-nussbaum.net> wrote:
> Relevant part:
> > /bin/sh ../libtool --mode=compile gcc -g -O2 -I/usr/include/freetype2/ -I/usr/include/freetype2 -I/usr/include/libxml2/ -I/usr/include/cairo -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2   -pthread -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12    -I/usr/include/python2.6 -I../inc -I../inc -I/usr/pkg/include -I/usr/pkg/include/giflib -Wmissing-prototypes -Wunused -Wimplicit -Wreturn-type -Wparentheses -Wformat -Wchar-subscripts -DHAVE_CONFIG_H -c ArabicForms.c
> > eval: 1: base_compile+= gcc: not found

 I've got a same issue in freewnn package, it is caused by dash as /bin/sh
 since it cannot recognize += notation.

 We can avoid this FTBFS with CONFIG_SHELL=/bin/bash, but I wonder this 
 would be permitted or not.


 Hideki Yamane     henrich @ debian.or.jp/org

Reply to: