On Fri, 08 Feb 2002 10:34:27 +0100, Danny Backx wrote:
>They look terribly out of date.
>Could you grab the latest release from either
> http://www.lesstif.org
>or
> http://sourceforge.net/projects/lesstif
>
>If you're running Linux, then going for a binary might
>be easier. Otherwise the source is the only option.
>
> Danny
Unfortunately the quoted line looks similar what we actually
have in our recent installation docs...
Quoting the related section:
The LD_LIBRARY_PATH variable is to contain a colon separated list
of paths to be searched for shared libraries. This variable is
consulted before the information compiled by ldconfig, so even if
you have LessTif already installed on your system you can use this
variable to force the use of the newly built library.
An example setting for LD_LIBRARY_PATH:
$ LD_LIBRARY_PATH=/home/toshok/lesstif/libXm:/home/toshok/lesstif/libMrm
$ export LD_LIBRARY_PATH
If you have superuser access and want LessTif to be installed for
system- wide use, make sure the directory to which the libraries
were installed is listed in /etc/ld.so.conf. Then (as root) type
ldconfig -v
to make them available.
This is not really wrong, but requires that the person reading
it is able to understand and adjust that stuff.
And this a bit difficult since the lines above are really
misleading.
I'll change it in CVS. Example would be:
If you told configure to install e.g. in /home/mai
by running "configure --prefix=/home/mai" then you have to
use
$ LD_LIBRARY_PATH=/home/mai/lib:$LD_LIBRARY_PATH
$ export LD_LIBRARY_PATH
If you don't give any paths to configure you should check
the output when running "make install" since I'm currently
not sure whether the default location is really always
fixed (-> be aware of non-supported autoconf ports, etc.)
---
Alexander Mai
[EMAIL PROTECTED]
_______________________________________________
Lesstif mailing list
[EMAIL PROTECTED]
https://terror.hungry.com/mailman/listinfo/lesstif
