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:-( so for the moment i give it up this part of the packages.
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:-( so for the moment i give it up this part of the packages.
To be honest I don't really see the point in rebuilding this using EPEL. Since mingw is a cross-compile, whatever distro is used for the host OS should not materially impact the resulting binaries. So ignoring the lack of automake, if you build the same version of mingw-gtk2 on Fedora 8, Fedora 9, Fedora 10, EPEL-5 the resulting DLL should be the same.
Building stuff on EPEL only makes sense if you are going to build the actual version of GTK from EPEL-5 for mingw. Rebuilding the Fedora 9 version of GTK on EPEL-5 for mingw just seems like a waste of time.
Daniel
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:-( so for the moment i give it up this part of the packages.
To be honest I don't really see the point in rebuilding this using EPEL. Since mingw is a cross-compile, whatever distro is used for the host OS should not materially impact the resulting binaries. So ignoring the lack of automake, if you build the same version of mingw-gtk2 on Fedora 8, Fedora 9, Fedora 10, EPEL-5 the resulting DLL should be the same.
Building stuff on EPEL only makes sense if you are going to build the actual version of GTK from EPEL-5 for mingw. Rebuilding the Fedora 9 version of GTK on EPEL-5 for mingw just seems like a waste of time.
the problem comes when we've got an epel build host which create all packages (linux, windows, etc). in this case i'd like to use (and build) mingw32 on epel.
On Fri, Oct 31, 2008 at 02:38:16PM +0100, 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:-( so for the moment i give it up this part of the packages.
To be honest I don't really see the point in rebuilding this using EPEL. Since mingw is a cross-compile, whatever distro is used for the host OS should not materially impact the resulting binaries. So ignoring the lack of automake, if you build the same version of mingw-gtk2 on Fedora 8, Fedora 9, Fedora 10, EPEL-5 the resulting DLL should be the same.
Building stuff on EPEL only makes sense if you are going to build the actual version of GTK from EPEL-5 for mingw. Rebuilding the Fedora 9 version of GTK on EPEL-5 for mingw just seems like a waste of time.
the problem comes when we've got an epel build host which create all packages (linux, windows, etc). in this case i'd like to use (and build) mingw32 on epel.
You shouldn't do builds based on the host OS packages. If you use mock then you can use a CentOS/RHEL5 build host, and make mingw packages using a Fedora 9 based mock config. So no need to actually build anything against RHEL5 packages
Daniel
Daniel P. Berrange wrote:
On Fri, Oct 31, 2008 at 02:38:16PM +0100, 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:-( so for the moment i give it up this part of the packages.
To be honest I don't really see the point in rebuilding this using EPEL. Since mingw is a cross-compile, whatever distro is used for the host OS should not materially impact the resulting binaries. So ignoring the lack of automake, if you build the same version of mingw-gtk2 on Fedora 8, Fedora 9, Fedora 10, EPEL-5 the resulting DLL should be the same.
Building stuff on EPEL only makes sense if you are going to build the actual version of GTK from EPEL-5 for mingw. Rebuilding the Fedora 9 version of GTK on EPEL-5 for mingw just seems like a waste of time.
the problem comes when we've got an epel build host which create all packages (linux, windows, etc). in this case i'd like to use (and build) mingw32 on epel.
You shouldn't do builds based on the host OS packages. If you use mock then you can use a CentOS/RHEL5 build host, and make mingw packages using a Fedora 9 based mock config. So no need to actually build anything against RHEL5 packages
unfortunately i don't understand this:-( suppose i would like to put these packages into EPEL too. then where should i build those packages which get into EPEL-5?
ps. i like put these packages into EPEL-5 beacuse out software run on centos-5 and i'd like to recompile the same program to windows too. what's more i'd like to compile my program on centos-5. i hope now i'm getting clear.
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:-( so for the moment i give it up this part of the packages.
To be honest I don't really see the point in rebuilding this using EPEL. Since mingw is a cross-compile, whatever distro is used for the host OS should not materially impact the resulting binaries. So ignoring the lack of automake, if you build the same version of mingw-gtk2 on Fedora 8, Fedora 9, Fedora 10, EPEL-5 the resulting DLL should be the same.
Building stuff on EPEL only makes sense if you are going to build the actual version of GTK from EPEL-5 for mingw. Rebuilding the Fedora 9 version of GTK on EPEL-5 for mingw just seems like a waste of time.
or do you mean that we only need to build mingw32-binutils and mingw32-gcc on epel and use all other noarch packages compiled on fedora on epel too?
the problem here suppose i've got a program which run and compile on epel and would like to rebuild on windows too. imho then the above packages not the beast choice.
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
Daniel
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.
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.
-
Daniel P. Berrange -
Farkas Levente