Bartosz Oudekerk wrote:
Marco Casavecchia Morganti wrote:
I'm using hippo into a Solaris 10 machine and i had build aspell from
sources with a custom prefix directory.
My aspell program and libraries aren't into the standard /usr/local
directory, so I added the LD_LIBRARY_PATH to the environment of the
fortress when it starts the CMS (to accomplish libraries dependecies).
Wouldn't it be better to add the location of the libraries to
/etc/ld.so.conf and rerunning /sbin/ldconfig?
If you use Linux.. yes.
The problem was that the AspellWrapper.class launches the command line
aspell with a "custom" empty environment.
And so my aspell fails to load its shared libraries because it lacks
of the LD_LIBRARY_PATH environment variable..
At the end, I modified the AspellWrapper.java class to search into the
environment for the LD_LIBRARY_PATH variable and pass its value to the
aspell command line environment.
The patch does not modify the default behavior of the class.
I think this is a system administration issue, no patches should be
necessary, or am I missing something here?
This is an intresting poin of view.. ;O)
I prepared the patch because i run the CMS on a Solaris SPARC server and
that was the first thing i think about to solve the issue.
Anyway, it is possible to set something like ldconfig even on Solaris
systems.
Thanks.
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
