gtk2 on epel won't be easy

Farkas Levente lfarkas at
Sat Nov 1 13:16:54 UTC 2008

Farkas Levente wrote:
> Daniel P. Berrange wrote:
>> On Fri, Oct 31, 2008 at 01:52:08PM +0100, Farkas Levente wrote:
>>> hi,
>>> i try to build gtk2 (and it's requirements) for epel, but there is a big
>>> problem that many packages require automake-1.10 which is on fedora but
>>> not on rhel-5:-(
>> Also note to build mingw-gtk2 you need to have already built the same 
>> version of gtk2 natively, becuase the cross-compile build process
>> needs various native gtk tools to generate code. So you really need
>> to build mingw-gtk2 version which matches the gtk in RHEL5, at which
>> point the automake version is a non-issue, because older gtk2 will
>> work fine with the older automake in RHEL5
> i didn't realize it until now, but this means that most spec file should
> have to be modified to require versioned native libraries eg: in stead of:
> BuildRequires:  glib2-devel
> put
> BuildRequires:  glib2-devel = %{version}
> or
> BuildRequires:  glib2-devel >= %{version}
> since currently mingw32-glib2 compile without any problem with older
> glib2-devel host packages.

it seems only there packages require native packages for build:
- mingw32-atk
- mingw32-glib2
- mingw32-gtk2
- mingw32-libvirt (only gettext)
so add a patch for all of the above spec file into review request to
explicitly require versioned native packages (except for gettext since i
assume older versions also works in this case).

ps. as mingw32-expat was added as review req. and it can be added to
mingw32-python BuildPrereq too.

  Levente                               "Si vis pacem para bellum!"

More information about the mingw mailing list