Error when installing rpm

[Guest mahiles]

I try installing an rpm and recieve the following:

 

error: failed dependencies:

       /bin/sh   is needed by fglrx-glc22-4.3.0-3.2.8

       /bin/sh   is needed by fglrx-glc22-4.3.0-3.2.8

       /bin/sh   is needed by fglrx-glc22-4.3.0-3.2.8

       /bin/sh   is needed by fglrx-glc22-4.3.0-3.2.8

       ld-linux.so.2   is needed by fglrx-glc22-4.3.0-3.2.8

       libc.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libdl.so.2   is needed by fglrx-glc22-4.3.0-3.2.8

       libICE.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libm.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libpthread.so.0   is needed by fglrx-glc22-4.3.0-3.2.8

       libSM.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libX11.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libXaw.so.7   is needed by fglrx-glc22-4.3.0-3.2.8

       libXext.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libXmu.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       libXpm.so.4   is needed by fglrx-glc22-4.3.0-3.2.8

       libXt.so.6   is needed by fglrx-glc22-4.3.0-3.2.8

       /bin/bash   is needed by fglrx-glc22-4.3.0-3.2.8

       libc.so.6(GLIBC_2.0)   is needed by fglrx-glc22-4.3.0-3.2.8

       libc.so.6(GLIBC_2.1)   is needed by fglrx-glc22-4.3.0-3.2.8

       libc.so.6(GLIBC_2.1.3)   is needed by fglrx-glc22-4.3.0-3.2.8

       libdl.so.2(GLIBC_2.0)   is needed by fglrx-glc22-4.3.0-3.2.8

       libdl.so.2(GLIBC_2.1)   is needed by fglrx-glc22-4.3.0-3.2.8

       libm.so.6(GLIBC_2.0)   is needed by fglrx-glc22-4.3.0-3.2.8

       libpthread.so.0(GLIBC_2.0)   is needed by fglrx-glc22-4.3.0-3.2.8

 

This is actually happening in Slackware but thought the thread might get more attention if it was in this forum. I added the directory of the .so.X files to /etc/ld.so.conf and ran ldconfig but the same errors come up?

 

Please help..

[Qchem]

I'm not sure how well rpm works on non rpm distros - I'm guessing that rpm can't find the dependant packages (they are installed aren't they??). You could try and update the database - it's a long shot.....