Installing glib2-2.6.6-1 on FC3?
Axel Thimm
Axel.Thimm at ATrpms.net
Fri Dec 16 09:54:18 UTC 2005
On Fri, Dec 16, 2005 at 01:43:56AM -0700, Philip Prindeville wrote:
> Well, I tried the following:
>
> # rpm -vv -e --nodeps glib2-2.4.8-1.fc3 glib2-devel-2.4.8-1.fc3.i386
> # rpm -v -i http://dl.atrpms.net/all/glib2-2.6.6-1_12.rhfc3.at.i386.rpm
> http://dl.atrpms.net/all/libglib-2.0_0-2.6.6-1_12.rhfc3.at.i386.rpm
> http://dl.atrpms.net/all/libgthread-2.0_0-2.6.6-1_12.rhfc3.at.i386.rpm
> http://dl.atrpms.net/all/libgobject-2.0_0-2.6.6-1_12.rhfc3.at.i386.rpm
> http://dl.atrpms.net/all/libgmodule-2.0_0-2.6.6-1_12.rhfc3.at.i386.rpm
> http://dl.atrpms.net/all/glib2-devel-2.6.6-1_12.rhfc3.at.i386.rpm
--nodeps and -i are bad things. You may be missing required packages
now, and the rpm database will show up two glib2 installs, of which
one is overwritten by the other.
Only use -i with kernels!
> and it installed, but...
>
> Trying to do a build of GDM blew up, and I suspect other things will
> eventually over time as well (which reminds me: is there a good way to
> exorcise programs that dynamically link to glib2 and make sure they
> all perform in a reasonably sane manner?):
That's quite a lot.
# rpm -q --whatrequires libglib-2.0.so.0 | wc -l
227
And that's only the direct dependecy. There is no sane way to remove
glib2's shared libs.
> # ./autogen.sh
> /usr/bin/gnome-autogen.sh
> checking for autoconf >= 2.53...
> testing autoconf2.50... not found.
> testing autoconf... found 2.59
> checking for automake >= 1.5...
> testing automake-1.9... found 1.9.2
> checking for libtool >= 1.4.3...
> testing libtoolize... found 1.5.6
> checking for glib-gettext >= 2.2.0...
> testing glib-gettextize... not found.
> ***Error***: You must have glib-gettext >= 2.2.0 installed
> to build GDM. Download the appropriate package for
> from your distribution or get the source tarball at
> ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz
check out the config.log for the tesing done.
> Anyone have a .spec file to build GDM 2.13.0.3 on FC3 or any
> suggestions on how to go about that?
Pick the rawhide gdm spec and try to upgrade it, it might be easy.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20051216/6ee414ce/attachment.sig>
More information about the fedora-devel-list
mailing list