GTK+2.8.17 installation problem using checkinstall.

Synt4x_3rr0r · 05-03-2006, 08:30 PM

So after alot of searching and experimenting I successfully compiled GTK.
But when I'm running checkinstall to make a Slackware package of it, it gives me errors.

Here's the output:

Code:

make  install-data-hook
make[4]: Entering directory `/usr/local/progz/gtk+-2.8.17/modules/input'
/bin/sh ../../mkinstalldirs /usr/etc/gtk-2.0
../../gtk/gtk-query-immodules-2.0 > /usr/etc/gtk-2.0/gtk.immodules
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-ipa.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-ipa.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-ipa.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-ipa.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-am-et.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-am-et.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-am-et.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-am-et.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-xim.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-xim.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-xim.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-xim.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-cedilla.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-cedilla.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-cedilla.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-cedilla.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-thai-broken.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-thai-broken.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-thai-broken.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-thai-broken.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-inuktitut.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-inuktitut.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-inuktitut.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-inuktitut.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-viqr.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-viqr.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-viqr.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-viqr.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-er.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-er.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-ti-er.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-er.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-et.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-et.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-ti-et.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-ti-et.so: cannot open shared object file: No such file or directory
Cannot load module /usr/lib/gtk-2.0/2.4.0/immodules/im-cyrillic-translit.so: /usr/lib/gtk-2.0/2.4.0/immodules/im-cyrillic-translit.so: cannot open shared object file: No such file or directory
/usr/lib/gtk-2.0/2.4.0/immodules/im-cyrillic-translit.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.4.0/immodules/im-cyrillic-translit.so: cannot open shared object file: No such file or directory
make[4]: *** [install-data-hook] Error 1
make[4]: Leaving directory `/usr/local/progz/gtk+-2.8.17/modules/input'
make[3]: *** [install-data-am] Error 2
make[3]: Leaving directory `/usr/local/progz/gtk+-2.8.17/modules/input'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/usr/local/progz/gtk+-2.8.17/modules/input'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/usr/local/progz/gtk+-2.8.17/modules'
make: *** [install-recursive] Error 1

****  Installation failed. Aborting package creation.

Cleaning up...OK

Bye.

I have searched everywhere for anyone who has a similar problem but not found anything good.
Does anyone know what can be causing this?

Synt4x_3rr0r · 05-04-2006, 05:43 AM

Sorry, bump.
Doesn't anyone know anything about this? I really need help because many programs that i use needs GTK.

Aah, never mind. I just downloaded the packages from a Slackware mirror. But I wanted the newest build

Well it works anyway.

tomdkat · 05-04-2006, 04:09 PM

I'm a Slackware user and have installed GTK+ 2.8.17 from source but didn't make a Slackware package. Why do you feel the need to do so?

Peace...

Synt4x_3rr0r · 05-05-2006, 11:46 AM

Because I dont like to have the sourcecode folders laying around and it's much easier to unistall the software if something should happen to it.

Some applications sourcecode dont even have an option to uninstall it. It actually surprices me a little that you are a slackware user and doesn't use checkinstall.
But I guess everyone have their way of doing things.

tomdkat · 05-05-2006, 04:22 PM

Quote:

Originally Posted by Synt4x_3rr0r

Because I dont like to have the sourcecode folders laying around and it's much easier to unistall the software if something should happen to it.

I'm not sure I follow you on this. I downloaded gtk+-2.8.17 to my home directory, uncompressed it and installed it in /opt/gnome. Then I deleted the gtk+-2.8.17* files and I've got GTK+ up and running and no source laying around.

Where's the problem?

Quote:

Some applications sourcecode dont even have an option to uninstall it. It actually surprices me a little that you are a slackware user and doesn't use checkinstall.
But I guess everyone have their way of doing things.

You shouldn't have to UN-install a library if the apps that use it are running fine, so I'm not sure why you would bother with a full "package". Linux distros make packages so people can install parts of the app or library instead of the whole thing. For example, Apache can be installed with the files needed to just run it and without the files needed for other apps to be built against it. If you're building GTK+ and other stuff from source, you're gonna get EVERYTHING unless you turn stuff off when you configure it.

I've been able to migrate from a glib/gtk+ 1.2.5 system to a glibc-2.8.6/gtk+-2.8.17 system without any problems at all, outside of leftover libraries from previous installations (which aren't source files).

I honestly find it odd that an end user would create packages from source built apps for their own installation, considering they aren't distro maintainers. But, to each his own.

Peace...

Synt4x_3rr0r · 05-06-2006, 04:16 PM

Quote:

Originally Posted by tomdkat

I'm not sure I follow you on this. I downloaded gtk+-2.8.17 to my home directory, uncompressed it and installed it in /opt/gnome. Then I deleted the gtk+-2.8.17* files and I've got GTK+ up and running and no source laying around.

Where's the problem?

You shouldn't have to UN-install a library if the apps that use it are running fine, so I'm not sure why you would bother with a full "package". Linux distros make packages so people can install parts of the app or library instead of the whole thing. For example, Apache can be installed with the files needed to just run it and without the files needed for other apps to be built against it. If you're building GTK+ and other stuff from source, you're gonna get EVERYTHING unless you turn stuff off when you configure it.

I've been able to migrate from a glib/gtk+ 1.2.5 system to a glibc-2.8.6/gtk+-2.8.17 system without any problems at all, outside of leftover libraries from previous installations (which aren't source files).

I honestly find it odd that an end user would create packages from source built apps for their own installation, considering they aren't distro maintainers. But, to each his own.

Peace...

Hehe, yes I know off all this already :P
But I think it's easier to maintain packages. Like when I want to upgrade something i just compile the new version, makes a package of it and then types "upgradepkg packagename.tgz".
It's just alot easier. And removing packages is also much easier. "removepkg packagename.tgz"
I like to make things easy for myself

But now it really doesn't matter because I checked for updates to Slack the other day and guess which package that had been updated? GTK

To the latest version too, so all my compiling was to no use after all :P

Cheers.