On Sat, Apr 18, 2009 at 01:15:50PM +0300, Peter De Schrijver wrote:
> Package: exult
> Version: 1.2-14
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > CFLAGS="-I.. -DHAVE_CONFIG_H" gimptool-2.0 --build u7shp.c
> > Cannot run 'pkg-config --cflags gimpui-2.0'
> > make[3]: *** [u7shp] Error 1
Thanks for reporting.
The title is somewhat misleading, since it isn't necessarily pkg-config
that is failing. It may be gimptool-2.0's fault (libgimp2.0-dev
package), which is supposed to call pkg-config.
Build dependencies are correctly pulled, and pkg-config is installed, so
I'm not sure why gimptool-2.0 is failing on MIPS while it seems to work
fine on other architectures. The part of gimptool's code that seems to
be failing is apparently pretty straightforward (see tools/gimptool.c in
gimp's source package):
gchar *command = g_strconcat (program, " ", args, NULL);
FILE *pipe = popen (command, "r");
gchar line[1000];
if (pipe == NULL) {
g_printerr ("Cannot run '%s'\n", command);
exit (EXIT_FAILURE);
}
I don't have access to a MIPS machine, but it would be interesting to
know what's the output of running a simple `gimptool-2.0 -n --build
foo.c' or `gimptool-2.0 --build foo.c' (even if foo.c doesn't exist).
Does that work or does it complain about pkg-config? How about
`pkg-config --cflags gimpui-2.0'?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
