> I confirm what other suggested. Moving the file out of my msys 1.0/bin
> directory make it works fine.
Sure. Doesn't MSYS documentation tell very clearly that one should not
put *anything* else into MSYS's bin directory? If I recall correctly,
MSYS assumes that programs in its own bin directory are MSYS programs,
not native Win32 programs (remember, MSYS is a fork of Cygwin, and
really somewhat of a hosted operating system on its own), and they are
invoked in a special way.
> It's in my MSYS directory:
Don't try to use pkg-config and/or MSYS in a way that's not
intended. Don't install (unzip) other stuff into the MSYS hierarchy.
> I am able to make it work by moving pkg-config.exe in my project
> directory and creating a link project/lib/pkgconfig
> -> ../../../../lib/pkgconfig
You are making things way too complicated. What do you mean by link?
MSYS implements symlinks by copying (unlike "true" Cygwin, which uses
Explorer shortcuts), so when you think that you have created a link
you have actually created a copy.
Wouldn't it be much easier to just have a separate hierarchy \foo,
with pkg-config.exe in \foo\bin, .pc files in \foo\lib\pkgconfig,
GTK+, GLib etc headers in \foo\include, import libs in \foo\lib, DLLs
in \foo\bin, etc, and then add \foo\bin to PATH? (In MSYS you probably
also want to mount \foo at /foo.) (Replace "foo" with something more
descriptive, of course.)