Hi,
Sourcing vapor-setup.sh breaks python on my Linux (Gentoo). The use of the LD_LIBRARY_PATH forces the system to use the wrong version of python for any other software. And with incompatible changes in python versions like the "_sre" module and "MAXREPEAT" variables in this case, other software will just break.
Why does vapor-setup.sh need to setup something as intrusive as LD_LIBRARY_PATH system wide?
Philippe
Hi Philippe, The settings to your LD_LIBRARY_PATH should only apply in the shell where you source vapor-setup.sh . It will not apply system-wide unless you source vapor-setup.sh every time you launch a new shell. You should be able to run your other Python environment in another shell at the same time you run VAPOR.
-Alan
Hi Alan,
That is absolutely right. But it might be worth thinking about removing the following part of the install guide or add a warning:
"For convenience it is advised that users place this command in their login
script (.login for C shell or .profile for other shells). Once the variables are set in the
login script, there is no need to run the environment script files for each session. "
I didn't expect these kind of advises to break unrelated parts of my system. It might save some headaches ;)
Philippe
my 7770 is a 3.0 card and my board only has pcie 2.0 is there a performance loss?
___________
http://www.lacyarnoldleanmomsreview.com/lacy-arnold/
We are aware of the problems on Linux with shared libraries. We hope to have a better solution for addressing portable executables on Linux in an upcoming release. In the interim we recommend not sourcing vapor-setup from you login script, and instead sourcing it from a separate terminal window as needed.