Op dinsdag 28-07-2009 om 12:39 uur [tijdzone +0200], schreef Paolo Bonzini:
AM_PATH_GLIB_2_0 will detect mismatched header files vs. installed libraries, while PKG_CHECK_MODULES, so your solution is not 100% equivalent.
So far, in us packaging about 100 packages (many dependent on glib), this has not proved a problem.
Because you do not have Wine installed, so that check is not run. A user (not a fedora packager) will have it 99% of the time.
That's strange. I do have wine installed here (with the binfmt stuff enabled) and I've never seen that behaviour when using ./configure --host=i686-pc-mingw32
Do you have glib2-devel? That's needed for the bug to trigger for my demo.
Also, you need very up-to-date libglib2. glib2 was updated to a newer 2.20.z release after F11, but mingw-glib2 wasn't.
I just tried to reproduce your testcase and I see the problem. However, I don't blame the Fedora-MinGW toolchain for this, but just the fact that the AM_PATH_GLIB_2_0 macro (provided by /usr/share/aclocal/glib-2.0.m4 / glib2-devel) isn't cross-compile aware. It provides an option called --disable-glibtest to disable the runtime tests, but it isn't activated when a cross-compile is requested.
The test program itself which is used in that macro is also not platform-independent as it depends on a binary tool called 'touch' being be available on the platform which obviously isn't the case for Win32.
The best place to get this fixed would be in glib2 itself, not here.
Most (if not: all) other packages which use GLib use the PKG_CONFIG_CHECK macro to find out if glib is installed and whether the version of it is recent enough. It looks like X-Chat is just one of the few programs which has been using the AM_PATH_GLIB_2_0 macro. AFAIK none of the packages in our MinGW toolchain appear to use this macro. Perhaps you might want to patch X-Chat so that PKG_CONFIG_CHECK is used instead of AM_PATH_GLIB_2_0.
Regards,
Erik van Pienbroek