When you get a segmentation fault while installing a package using RPM, most of the times it is because of depency failure(s) in one of the packages used by RPM itself (directly or indirectly).
You can check depencies with
$ rpm -V --nofiles --nomd5 -a
I've spent 2 days to learn how packages and depencies can mess up my system, and how to get it back on track. It is a matter of trial and error, in- and uninstalling the right packages. Too high versions require to much other packages, and too low ones don't provide the needs you want.
When RPM fails installing, you can try it with another package manager like KPackage. For RPM 4.1 on a RedHat 7.x system for example you need the following rpmfiles:
- popt-1.7-1.07.7x.i386.rpm
- rpm-4.1-1.07.7x.i386.rpm
- rpm-build-4.1-1.07.7x.i386.rpm
- rpm-python-4.1-1.07.7x.i386.rpm
Install these at the same time as they depend on each other:
$ rpm -Uvh popt-1.7-1.07.7x.i386.rpm \
rpm-4.1-1.07.7x.i386.rpm rpm-build-4.1-1.07.7x.i386.rpm \
rpm-python-4.1-1.07.7x.i386.rpm
where \ denotes a whitspace
A good site where you can search for RPM's by name or by files needed, including wildcard options is
http://rpm.pbone.net/I cannot explain directly how you can get rid of the error, because some more information of your specific linux installation is required. You can get this information by the information above, so feel free to post more specific details.