[SOLVED] Gparted installed in Slackware 14

lkraemer · 10-03-2012, 01:03 PM

I've installed Gparted in Slackware 14 from slackfind.net.

Quote:

gparted-0.13.1-i486-1sl
Slackware-13.37 / slacky.eu
location: system/gparted/0.13.1
dependencies: atk >= 1.32.0-i486-1,atkmm >= 2.22.5-i486-1sl,cairo >= 1.10.2-i486-2,cairomm >= 1.9.8-i486-1sl,cxxlibs >= 6.0.14-i486-1 | gcc-g++ >= 4.5.2-i486-2,expat >= 2.0.1-i486-2,fontconfig >= 2.8.0-i486-1,freetype >= 2.4.4-i486-1,gcc >= 4.5.2-i486-2,gdk-pixbuf2 >= 2.23.3-i486-1,glib2 >= 2.28.6-i486-1,glibc-solibs >= 2.13-i486-4,glibmm >= 2.27.99.2-i486-1sl,gtk+2 >= 2.24.4-i486-1,gtkmm >= 2.24.0-i486-1sl,libX11 >= 1.4.3-i486-2,libXau >= 1.0.6-i486-1,libXcomposite >= 0.4.3-i486-1,libXcursor >= 1.1.11-i486-1,libXdamage >= 1.1.3-i486-1,libXdmcp >= 1.1.0-i486-1,libXext >= 1.2.0-i486-1,libXfixes >= 5.0-i486-1,libXi >= 1.4.2-i486-1,libXinerama >= 1.1.1-i486-1,libXrandr >= 1.3.1-i486-1,libXrender >= 0.9.6-i486-1,libpng >= 1.4.5-i486-1,libsigc++ >= 2.2.9-i486-1sl,libxcb >= 1.7-i486-1,lvm2 >= 2.02.84-i486-1,pango >= 1.28.4-i486-1,pangomm >= 2.28.2-i486-1sl,parted >= 2.3-i486-1,pixman >= 0.20.2-i486-1,udev >= 165-i486-2,util-linux >= 2.19-i486-1,yelp >= 2.30.1-i486-5sl,zlib >= 1.2.5-i486-4

I'm getting this error:

Code:

which gparted
/usr/sbin/gparted

/usr/sbin/gparted
/usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory
bash-4.2#

How do I get Gparted to execute?

Thanks.

Larry

Didier Spaier · 10-03-2012, 01:16 PM

Install gtkmm.

I would recommend when you miss a package to first look at the availability of a SlackBuild for it @ slackbuilds.org. You will find information in their FAQ how to use it to make yourself a package and for every application they do list the dependencies when they are not part of a full installation of Slackware.

EDIT At first I wrote slackbuilds.net instead of slackbuilds.org, sorry about that. So basically my advise is the same as Ponce's. He just worded it better

ponce · 10-03-2012, 01:25 PM

it seems to me that you installed the package from the 13.37 repository of slacky.eu.

don't expect to pick packages here and there (from different sources and for different versions of slackware) and just hope they work together

the best suggestion I can give you is to install it from the build scripts on slackbuilds.org (but first install the dependencies -in the right order).

Beelzebud · 10-03-2012, 01:55 PM

I installed Gparted just last night, using slackbuilds.org, and it works fine for me. You just have to make sure you have installed all of the dependencies required. If you're using slackbuilds.org website, always look for the listed dependencies.

For instance Gparted says it relies on gtkmm, and gtkmm relies on mm-common and atkmm, which in turn have their own dependencies.

yars · 10-03-2012, 02:44 PM

If I find myself in this situation, the first thing I'm doing - looking package that contains the file that caused the problem, using slackpkg:

Code:

# slackpkg file-search filename.so

But it is not always, as in this case, gives the desired result. Then I look in google by filename. Typically, it is helps.

lkraemer · 10-03-2012, 03:29 PM

Didier Spaier, ponce, Beelzebud, yars:
Thanks for the information. I removed the gparted package from Slackware-13.37 / slacky.eu

I've downloaded the dependencies (source & script) from SlackBuilds.org
I'm going to attempt it a bit later.

I had previously built and installed PSI from there.

THANKS for the help.....I'll get there.....

Larry

slackass · 10-03-2012, 06:20 PM

Another option would be partitionmanager in /extra.
Works good, no deps.

lkraemer · 10-03-2012, 07:19 PM

Beelzebud,
I'd like to ask you a question on how you organize the dependencies.

I've got a listing of the dependencies:

Quote:

Gparted (0.13.1) requires -> gtkmm -- gtkmm requires -> mm-common & atkmm

atkmm requires -> pangomm -- pangomm requires -> cairomm -- cairomm requires -> glibmm

glibmm requires -> libsigc++

Do you create a gparted folder and lump everything in there and build via the script for each dependecy,
or do you have each dependency in it's own folder and just copy the built dependency from the tmp folder
to the gparted folder. I don't want to end up unorganized, and have multiple copies, floating around.

Or maybe you have another completely different method. What's the best method?

Thanks.

Larry

willysr · 10-03-2012, 07:44 PM

in SlackBuilds, you have different folders for each package. You can follow that method
it simplifies your package structure on your local directory

vigi · 10-03-2012, 10:47 PM

Just wondering why it is neccessary to install in a correct order?
I usually install the package first and rely on the system to tell me want it needs via the error messages.

Beelzebud · 10-03-2012, 11:09 PM

I highly recommend using sbopkg (www.sbopkg.org), as it automates a lot of the tedious stuff. As to the order, it just depends on what you're installing. Some things won't build without their dependency already on the system, in the case of a needed library, etc.

At any rate, sbopkg will greatly simplify the process.

ponce · 10-04-2012, 02:17 AM

Quote:

Originally Posted by lkraemer

I've got a listing of the dependencies:

Do you create a gparted folder and lump everything in there and build via the script for each dependecy,
or do you have each dependency in it's own folder and just copy the built dependency from the tmp folder
to the gparted folder. I don't want to end up unorganized, and have multiple copies, floating around.

Or maybe you have another completely different method. What's the best method?

personally I install sbopkg, I sync with "sbopkg -r" and I build/install things in the reverse order you mentioned (so that the next entry of the queue I build will have all the dependencies needed -to answer also to vigi)

Code:

sbopkg -i "mm-common libsigc++ glibmm cairomm pangomm atkmm gtkmm gparted"

gmgf · 10-04-2012, 03:21 AM

It seem mm-common isn't needed for gtkmm now:

http://ftp.gnome.org/pub/gnome/sourc...mm-2.24.2.news