On Sat, Apr 18, 2009 at 08:03:48PM +0200, Jordà Polo wrote:
> 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'?
This bug has been sitting here for too long and is stopping a much
better version of exult from getting into testing.
As explained in my previous message, 1) I don't have a MIPS machine and
can't reproduce the bug, 2) it looks like some other tool is failing in
a very straightforward step, and 3) there have been new releases of
libgimp2.0-dev since the bug was reported. I really need some feedback
here, I'm not even sure if the problem is still present.
Thanks.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
