You need the devel packages for those libraries. Note that SuSE 9 personal edition doesn't have the devel packages; they're only included with the professional edition. (This strikes me as kind of dumb.) You can get them from the FTP site, though.

I have the professional edition, but in at least one case that I looked, SuSE is using an older version of the library than is RedHat.

First, it looks like the i386.rpm didn't install because you've got an older/newer version of OpenSSL (I forget which right now). Depending on what distro that i386.rpm was compiled on, it was linked against OpenSSL 0.9.6 or 0.9.7, which seems to have changed the library version, and hence the filename.

Also, it looks like what it's really missing is the libxml-2.0 development package. Under RedHat (SuSE may be the same way), libxml and libxml-devel are separate packages. To compile from source, you need the -devel version of that package installed along with the regular version (often you have to do this by hand because the installer doesn't install devel packages by default). Also (And this is what has confused most of my friends before) is that when ./configure says it's looking for whatever package, it actually means the -devel version of that package.

I have libcom_err.so.2 - the rpm asks for libcom_err.so.3
I have libcrypto.so.0.9.7 - the rpm asks for libcrypto.so.4
I have libgssapi.so.1- the rpm asks for libgssapi_krb5.so.2
I don't have libk5crypto.so.3, at least not anything with a similar name.
I have libkrb5.so.17 - the rpm asks for libkrb5.so.3
I have libpspell.so.15 - the rpm asks for libpspell.so.4
I have libssl.so.0.9.7 - the rpm asks for libssl.so.4

SuSE spells libxml-2 as libxml2, which might cause errors with ./configure even though I have the devel packages installed.

On my system, libcom_err.so.3 is owned by krb5-libs-1.3.1-6, libcrypto.so.4 is a symlink to libcrypto.so.0.9.7a, libgssapi_krb5.so.2 is also owned by krb5-libs-1.3.1-6, and it seems like the majority of them are compile-time options in the security libs. As for the libxml-2 vs libxml2, that's possible. If the .pc (IIRC) file isn't named the right way, pkgconfig can't find it, however, if you symlink it, it may just get past that.