On 05/13/2012 11:55 AM, Jakub Wilk wrote: > tags 671971 + patch > thanks > > * Lucas Nussbaum <lucas@lucas-nussbaum.net>, 2012-05-08, 14:10: >>> /bin/sh ../libtool --mode=compile gcc -g -O2 -fstack-protector >>> --param=ssp-buffer-size=4 -Wformat -Werror=format-security >>> -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/x86_64-linux-gnu/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/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 >>> -I/usr/include/freetype2 -I/usr/include/libpng12 >>> -D_FORTIFY_SOURCE=2 -I/usr/include/python2.7 -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 >>> ../libtool: 1: eval: base_compile+= gcc: not found >>> ../libtool: 1: eval: base_compile+= -g: not found >>> ../libtool: 1: eval: base_compile+= -O2: not found > > The attached patch fixes this bug. After applying it you can also safely > drop CONFIG_SHELL export from debian/rules. I might be misunderstanding this patch -- i think the intent is to cope with the bashisms in some of the configuration scripts, but the patch doesn't mention bash at all. Is it attempting to rely on the user's shell being bash? If so, What if the user's shell is /bin/sh (and that's symlinked to dash) or some other shell? --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature