Re: [Modules] Strange LD_LIBRARY_PATH issue with 3.1.6 on RedHat 7.1

[Leo B. <lb...@br...>]

Leo Butler (lb...@br...) wrote:

> A funny thing happened very suddenly on our Linux servers
> that I'm at a loss to explain.  The basic problem is this:
>
> RedHat 7.1, modules 3.1.6
>
> Log into a Linux system, load up several modulefiles for
> some EDA software, then try to run another module command
> and we get the error:
>
> init.c(425):ERROR:159: Cannot initialize TCL
>
> Turns out the reason this happens is due to adding a new
> library to the LD_LIBRARY_PATH from one of the EDA tools,
> DesignSync from Synchronicity "lib.Linux".  Take that out
> of the LD_LIBRARY_PATH and modules starts working again.

The issue is resolved.  The Synchronicity tools don't need
to have the lib.Linux path set in the LD_LIBRARY_PATH, so
I can remove it and the correct libtcl8.3.so will be found
in /usr/lib instead of down inside the Synchronicity lib
directory.

I also found that putting /usr/lib up front in LD_LIBRARY_PATH
took care of the issue as well.  Interesting that 3.1.5
didn't care about what was in the LD_LIBRARY_PATH but 3.1.6
did; both versions were generated using dynamic libraries,
so it wasn't because of that.

Regards,

- Leo Butler