Matthew Jarvis wrote:
> I am assuming that these versions of files are good enough for what OO
> is looking for...
DSO versioning. I do not know of a document to point you at, sorry.
But yes, if the library maintainers are versioning their libraries
correctly, you have the libraries you need.
libfoo.so is a library, no version. An app's makefile should specify
libfoo.so and resolve to a particular version at link time.
libfoo.so.7 is the 7th version of the ABI. A linked app will
reference libfoo.so.7, so that any libfoo.so.7 will work with it.
libfoo.so.7.1 or libfoo.so.7.1.13.6.55.3 is a specific released
version of the library. It implements the 7th version of the
ABI.
> I am assuming that if I copy these to the right place (or change a path
> or something) that OO can find them... or, are these like Windows dll's
> and need to be registered in some way?
Yes, that's correct. There should be symlinks from the actual library
to the ABI name and the generic name. It appears that you don't have
those.
> Which should I do and how should I do it?
First of all, why do you have files in /backup/opt and not in /opt?
Unless /opt is a symlink, you need to get the whole openoffice
distribution into /opt.
Then, create the symlinks for the dso's. Something like this.
cd /opt/openoffice.org-2.0/program
ln -s libuno_sal.so.3.* libuno_sal.so.3
ln -s libuno_sal.so.3 libuno_sal.so
(repeat for the other two.)
OO.o should work at this point. If not, you're going to have to bang
on your library path.
--
Bob Miller K<bob>
[EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
