Closed doutriaux1 closed 3 years ago
Adding:
export LD_LIBRARY_PATH=/usr/tce/packages/gcc/gcc-4.9.3/lib64
To my path fixed the loading issue. (figured out this path by using ldd
on the problematic library
I would still like to hera about using visit -cli and argparse together though.
Or how to specify a specific version of visit, right now I need the 'visit' executable to be in my path, but pointing to /usr/gapps/visit/3.1.3 does seem to find ny visit
executable.
The std lib path issue is a result of the system python being compiled with different compilers and or different settings than VisIt's python. Glad you could fix with LD_LIB, depending on how much the compilers or the config args change between the two, importing might not even be possible.
visit uses the same launcher to launch all installed version.
If you want the equiv of:
/usr/gapps/visit/bin/visit -v 3.1.3
You could use:
visit.AddArgument("-v 3.1.3")
Before the call to:
visit.LaunchNoWin()
Hello,
I have a python script that uses both visit and argparse up until this week my script had the following lines to make it work
And everything worked fine with my regular python
But today the
visit.LaunchNoWin()
line returns (on rztopaz and rzalastor):visit launches fine from the command line. So I figured I would just launch via -cli -s
Unfortunately using
Leads to mangling of the
-s
options and other options seems to be passed to visit as well.So my question are
GLIBCXX_3.4.20' not found
Thanks.