Re: Help locating an rpm for libexpat.so.0 ???


bobmct wrote:
However, when I try to
install it I get complaints of a dependency failure of libexpat.so.0 which
I do not have. I DO have libexpat.so.1.5.0 and a symlink of libexpat.so.1
for it which I have tried various symlink tricks but cannot get by it.
Also, searches of the same at various repositories come up empty.

I had exactly the same problem when I first installed SUSE 10.1.
Unfortunately, I can't remember for the life of me how I got round it!!
I do know I have a libexpat.so.0.5.0 in /usr/lib64 and a symlink to
that file called libexpat.so.0, and I vaguely remember creating that
symlink. Do a search for the 0.5.0 file on your machine and create the
symlink as usual, that should sort it.

I do know that I didn't install or build the library as I don't have
the source or the rpm for it.

HTH. If I remember anything else, I'll let you know.

.

Relevant Pages

  • coreutils-6.10 released (stable)
    ... run a command like this: ... tr's case conversion would fail in a locale with differing numbers ... "make install" no longer attempts to install su. ... chmod no longer ignores a dangling symlink. ...
    (gnu.announce)
  • Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
    ... symlink to packages/, use GNU stow, and that's how I maintain ... - you can have apps with dashes in the names without ambiguity. ... (You still have to pick a name for the packages/ symlink, ... install. ...
    (uk.comp.os.linux)
  • Re: disable init scripts
    ... > It is very easy to install them again. ... >> Install and use sysvconfig. ... Instead keep the symlink but rename it. ...
    (Debian-User)
  • Re: A Year with Linux
    ... but I believe what Enrique *meant* was "How easy is it to install ... Ubuntu is Debian-based, and the Debian people ... One thing that seems to confuse a lot of people is the plugin directory ... create that symlink; I don't remember now as I installed the silly thing ...
    (comp.os.linux.misc)
  • Re: Flash no longer displayed in Firefox
    ... > find out that the symlinked plugins dir was to blame. ... > browser_linux_plugins and mozilla worked again. ... the symlink was so plugins would install in the proper directory and save ... remove the symlink after installing pluginwrapper. ...
    (freebsd-questions)