[GRASS5] Debian and d.m/d.zoom bug - /etc/ld.so.conf

Markus Neteler neteler at itc.it
Wed Dec 1 10:49:52 EST 2004


On Wed, Dec 01, 2004 at 01:31:16PM +0000, Paul Kelly wrote:
> On Wed, 1 Dec 2004, Markus Neteler wrote:
> 
> >On Wed, Dec 01, 2004 at 01:18:59PM +0000, Paul Kelly wrote:
> >>On Wed, 1 Dec 2004, Markus Neteler wrote:
> >>
> >>[...]
> >>>d.m is now updated in CVS.
> >>>Debian users: please try again (don't forget to revert the 
> >>>/etc/ld.so.conf
> >>>change
> >>>for testing, run ldconfig as well).
> >>>
> >>>I had to modify lib/init/grass-run.sh to make it working for Fedora:
> >>>
> >>>LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"$GISBASE/lib"
> >>>               ^^^^^^^^^^^^^^^^^-added
> >>>
> >>>Hopefully this problem is resolved now.
> >>
> >>Well in general it looks like it should just be passing on the current
> >>LD_LIBRARY_PATH (whatever that contains). Would something like
> >>exec xterm -e LD_LIBRARY_PATH=$env(LD_LIBRARY_PATH) d.zoom
> >>(in the Tcl code) not work?
> >>
> >>And there is also the problem (noted in Glynn's original e-mail) that e.g.
> >>LD_LIBRARY_PATH is called different things on different platforms, e.g.
> >>DYLD_LIBRARY_PATH on OS X. But this can be fixed by dynamically
> >>substituting the correct variable name in at compile-time like is done for
> >>lib/init/init.sh
> >>
> >>Paul
> >
> >[isn't it easier to handle such necessary conditions in grass-run.sh
> >rather than messing up d.m.tcl? ]
> 
> The thing is we are assuming LD_LIBRARY_PATH has been unset by the time 
> grass-run.sh is run, and we need to set it again. So your change doesn't 
> really make sense as on the systems that have the problem, 
> $LD_LIBRARY_PATH will already be empty by that stage. I was thinking if we 
> need to pass on an already existing LD_LIBRARY_PATH, it needs to be 
> evaluated before xterm is run as that is what unsets it.

I simply took the proposed suggestion to make things happen (it was
suggested month ago).
 
> I'm not sure enough to make a change, just want to add to the discussion 
> and have it documented!

OK, so we both leave it to someone else :-)

Markus




More information about the grass-dev mailing list