Across machines maybe. But what about on the same machine?
Take an example:
I am sick of the number of people who can't run xv on the acs machines
simply because xv can't find the shared lib.
Add LD_LIBRARY_PATH=/usr/local/lib in the global .login file. This is how
it has been solved to an extent.
Link -R/usr/local/lib the xv binary.
The second is much neater and guards against users stuffing around with
their environment variables. Not to mention the fact that the first
way requires root privs.
> (Do you REALLY have paths hard coded into all of your binaries? Certainly
> in my work environment, predominantly Solaris, nothing does. Everything
> depends on the LD_LIBRARY_PATH, consequently one binary will run
> anywhere, you can even do library development without upsetting the
> public copy of a library. Yes I know about the security ramifications...)
So everyone should have LD_LIBRARY_PATH=/student/ele/ablancha/lib just
to run my binaries? My work environment is predominantly at uni :)
-- Anton Blanchard email@example.com Electrical Engineering Student firstname.lastname@example.org University of Technology, Sydney http://www.progsoc.uts.edu.au/~anton
Well, it's a laugh, innit?