<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
P.S., this is handy:<br>
yum whatprovides */glibmm-2.4.pc<br>
<br>
- under RHEL as opposed to CentOS you may need to do this as a user
with permission to access the RHN plugin (e.g. root).<br>
<br>
Ian Malone wrote:
<blockquote cite="mid:5149966E.2010007@ucl.ac.uk" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<title></title>
On RHEL6 there's glibmm24-devel and gtkmm24-devel, but they're in the
rhel-x86_64-workstation-optional-6 repo, which you may not have enabled
for your system (need to do that through the RHN channel management I
think).<br>
<br>
Henry Mensch wrote:
<blockquote cite="mid:09D331AA-E4AC-44B4-875C-FE006CC375E2@va.gov"
type="cite">
<pre wrap="">That's what I expected, too, but RHEL doesn't come with the -devel bundles for this stuff:
[root@musca dx-4.4.4]# yum -y install gtkmm24-devel
Loaded plugins: refresh-packagekit, rhnplugin
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Install Process
No package gtkmm24-devel available.
Error: Nothing to do
[root@musca dx-4.4.4]# yum -y install gtkmm24-devel-2.18.2-1
Loaded plugins: refresh-packagekit, rhnplugin
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Install Process
No package gtkmm24-devel-2.18.2-1 available.
Error: Nothing to do
[root@musca dx-4.4.4]# yum -y list gtkmm\*
Loaded plugins: refresh-packagekit, rhnplugin
This system is receiving updates from RHN Classic or RHN Satellite.
Installed Packages
gtkmm24.x86_64 2.18.2-1.el6 @anaconda-RedHatEnterpriseLinux-201009221801.x86_64/6.0
so it's not clear to me where what you found actually comes from.
On Mar 19, 2013, at 4:10 PM, Donald Tournier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">OK, I just did a very quick search and I think I know where the problem is. These packages typically come in pairs: runtime and development. The runtime would only contain the libraries, and the development package should contain everything needed to compile against it, including headers and hopefully the relevant pkg-config file. I came across this on my search: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://pkgs.org/centos-6-rhel-6/centos-rhel-i386/gtkmm24-devel-2.18.2-1.el6.i686.rpm.html">http://pkgs.org/centos-6-rhel-6/centos-rhel-i386/gtkmm24-devel-2.18.2-1.el6.i686.rpm.html</a> - looks like it might fit the bill...?
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>