$ rpmbuild --rebuild gabber-0.8.7-1.src.rpm
[snip]
checking for catalogs to be installed... az ca da de
el es fi fr ja ko lt ms nl no pl pt ro ru sk sv tr uk zh_TW
sed: can't read ./intl/po2tbl.sed.in: No such file or
directory
checking for libglade >= 0.11... 0.16 found
checking for GAL >= 0.3... 0.8 found
checking for gtkmm-config... /usr/bin/gtkmm-config
checking for GTK-- - version >= 1.2.5... no
*** Could not run GTK-- test program, checking why...
*** The test program failed to compile or link. See the
file config.log for the
*** exact error that occured. This usually means GTK--
was incorrectly installed*** or that you have moved
GTK-- since it was installed. In the latter case,
you*** may want to edit the gtkmm-config script:
/usr/bin/gtkmm-config
configure: error: Cannot find gtkmm 1.2.5 or greater.
error: Bad exit status from /var/tmp/rpm-tmp.50945 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.50945 (%build)
$ gtkmm-config --version
1.2.8
Huh?
All of the required libraries are installed from the
Red Hat RPMs, with the following exceptions being from
Ximian:
gtkmm-devel-1.2.8-1.ximian.4
gnomemm-1.2.2-1.ximian.1
gnomemm-devel-1.2.2-1.ximian.1
gtkmm-1.2.8-1.ximian.4
Logged In: YES
user_id=9539
It's not a problem with the SRPM. The problem is as it says:
it could not compile and run a gtkmm test program. This is
usually because gtkmm was incorrectly installed (as in,
getting mandrake RPMs for rh7.2 or changing your gcc or
something like that -- libsigc++, gtkmm, gnomemm must have
been compiled on the exact same gcc version you are using).
On some setups, the gtkmm test program has been known to
fail when Gabber will still work, so you can use the
--disable-gtkmmtest configure flag.