[Nottingham] k3b install, yum, gcc and libs

David Wolfson eaxdrw at nottingham.ac.uk
Thu Sep 16 10:43:40 BST 2004


The good news here it that I've finally got hold of the old drive I needed to set up dual boot at home.  For want of a reason to get hold of another distro, I've installed RH9 which seems to be pretty happy on the whole.  I've installed yum and updated the system (nearly 200 updates!) and all still seems happy.  Next thing I tried (as it seemed like a good idea) was to try installing k3b.  Now life gets interesting.  

Having been to the k3b website, I followed the advice for redhat there to used yum or apt to do the install.  I added the relavant lines to the yum.conf file and tried:
#yum install k3b
(all very sensible I think).  This came up with a list of about 6-8 dependancies that were not provided.  I decide that this is a good opotunity to get to grips with rpms, and an hour or so later the list was down to just one:
libselinux.so.1

<aside>
during this process I ended up rebooting the system a couple of times, which seem a little too microsoft for linux.  I know that in certain situations you can simply resart relavant services, but what if you don't know which ones to restart?  
</aside>

So I got hold of, and ran 'libselinux-1.11.4-1.sh4.rpm', which said it needed 'libc.so.6(GLIBC_2.3.4)'.  After some googling I decided that thiwas a gcc library (and here I start to make it up a bit), and found it in /lib.  So as this didn't work I decided that it wanted one from gcc version 2.3.4.  I then (prehaps foolishly?) decied to get hold of said version of gcc.  Many hours of compling later (in /opt for want of a better place) #gcc --version says that I now have gcc 2.3.4.  So, did this work?  Nope.  

I'm now at a bit of a loss, and have pretty much exhusted adivce from googling.  Any ideas please?  It's not critical to get k3b up and running, but I've got a long way to sorting it out and would like to finish it off.

The only other thing that confuses me is what acrhitecture I'm running on.  Other than the fact they are different and it matters for various rpms. I don't really know the difference, but #uname -p gives i686 but when I run yum, it looks on the RH-i386 servers...

Cheers for the advice,

Dave

PS - are any slides/stuff from recent talks available on the web. I can see stuff up to 2002....


This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks.  Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.




More information about the Nottingham mailing list