On my systems, the library file itself is installed by the “expat” package. Assuming that package is in your system, ‘rpm -q -l expat’ will show you the files it installs. The file with more than one dot-plus-number after the .so is the actual file itself. The name with only one dot-plus-number after the .so would be a symbolic link to the actual file.

Somewhere the FBReader package will have a large executable file (mine is called “FBReader”). Do ‘ldd appropriate_path/FBReader’.
That will tell you what the executable is looking for. If the “expat” package does not have this, quick_and_dirty is to add a symbolic link to provide it. [For instance, what I have is “/lib/libexpat.so.1.5.2″. If I needed “libexpat.so.0″, I would (as root) enter ‘ln -s /lib/libexpat.so.1.5.2 /lib/libexpat.so.0′.

I got my FBReader from Dov’s site – there were two versions, and I got what was the latest at the time (it looks for “libexpat.so.1″).
—
Hope that helps someone along their quest to install fbreader!

Rachel, I still haven’t found an answer to your question about the XO reading content within zip files with FBReader, but it works on other laptops so I’m not sure what the story is there. Robert Nagle has a great post about the XO as an ebook reader at http://www.teleread.org/blog/2007/11/12/free-olpc-ebooks-for-children-ebook-specs-for-xo-laptop/, that mentions zip being renamed to xol, but I don’t know how that would “fix” it for FBReader. Anyway, I’ll keep looking around and see what I can find out.

I had already gotten decent results by just adjusting the line spacing to its maximum possible value in the FBReader options, but having it be ‘right’ will be nice too I assume he’s submitted it as a patch so future versions of FBReader will have it.