You are not logged in.
I'm trying to work with Salome (http://www.salome-platform.org/) and it requires Python 2.7.10. Currently python2 is 2.7.13, how can I install 2.7.10?
Offline
There's very little chance it doesn't work with 2.7.13 if it works with 2.7.10.
Offline
Yea, you'd think, but it doesn't. I get the same error as in this thread https://www.code-aster.org/forum2/viewt … 271#p52271 and the solution here: https://www.code-aster.org/forum2/viewt … 381#p52381 says to use 2.7.10 so I'd like to give it a try.
Offline
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
Yeah, don't downgrade something like this.
Try the salome packages in the AUR. If nothing else, use a virtual environment like the linked thread says.
Offline
Oops, I guess downgrading python would be a bad idea. I thought he wanted to downgrade salome for some reason. Clumsy me.
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
I was hoping there'd be a way to Install 2.7.10 beside 2.7.13?
Offline
use a virtual environment like the linked thread says.
Offline
So I downloaded Python 2.7.10 sources built them with the prefix=home/wink/python-2.7.10. I then tried to run virtualenv2:
$ virtualenv2 -p /home/wink/python-2.7.10/bin/python python-2.7.10-venv
Running virtualenv with interpreter /home/wink/python-2.7.10/bin/python
ERROR:root:code for hash md5 was not found.
Traceback (most recent call last):
File "/home/wink/python-2.7.10/lib/python2.7/hashlib.py", line 147, in <module>
globals()[__func_name] = __get_hash(__func_name)
File "/home/wink/python-2.7.10/lib/python2.7/hashlib.py", line 97, in __get_builtin_constructor
raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type md5
ERROR:root:code for hash sha1 was not found.
....
Search the web I find this, it seems I don't have openssl1.0 runtime installed.
So I try to install openssl and I have 1.1.0 not 1.0.0
$ sudo pacman -Syu openssl
[sudo] password for wink:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
warning: openssl-1.1.0.f-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) openssl-1.1.0.f-1
Total Installed Size: 6.26 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] n
So I looked at what libssl I have:
$ ls -al /usr/lib/libssl*
-rwxr-xr-x 1 root root 361544 Jun 9 10:35 /usr/lib/libssl3.so
lrwxrwxrwx 1 root root 13 May 25 09:48 /usr/lib/libssl.so -> libssl.so.1.1
-r-xr-xr-x 1 root root 502024 May 25 09:54 /usr/lib/libssl.so.1.0.0
-rwxr-xr-x 1 root root 437920 May 25 09:49 /usr/lib/libssl.so.1.1
So it actually looks like I have libssl.so.1.0.0 but python 2.7.10 apparently isn't seeing it
Is this the right direction? Any suggestions on how to proceed?
Offline
So it actually looks like I have libssl.so.1.0.0 but python 2.7.10 apparently isn't seeing it
Is this the right direction? Any suggestions on how to proceed?
I believe the root cause is explained in that same StackOverflow topic, further down: your virtualenv compiled 2.7.10 was linked such that it can't find the right .so libraries. There's a couple of suggestions in that same topic on how to "fix" it, but this may be the first out of several .so issues you will run into.
Instead, I would suggest to look at patching Salome to work with the latest Python 2 instead. If you are truly in "dependency hell" with legacy .so libraries, patching Salome may actually be less work...
Offline
I'd already tried building Salome with 2.7.13 and it "worked", i.e. I was able to successfully compile 2.7.13 sources while building Salome. But then it wouldn't compile qt 5.6.1 which I'm guessing is because Arch is on qt 5.9.1 so it seems I'm in "dependency hell" on all paths
I'm going to try using docker, which I've only played with a very tiny bit, as I did find a docker image. My first attempt has failed:
$ sudo docker run -ti --rm -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v $HOME/.Xauthority:/home/developer/.Xauthority --env QT_X11_NO_MITSHM=1 --net=host --pid=host --ipc=host trophime/salome-8.2.0:nvidia salome
[sudo] password for wink:
Sorry, try again.
[sudo] password for wink:
runSalome running on wink-desktop
INFO:MainThread:Problem loading PortManager file: /opt/salome/appli_V8_2_0/USERS/.omniORB_PortManager.cfg
INFO:PortManager:Problem loading PortManager file: /opt/salome/appli_V8_2_0/USERS/.omniORB_PortManager.cfg
Searching for a free port for naming service: 2810 - OK
Searching Naming Service ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
File "/opt/salome/appli_V8_2_0/bin/salome/runSalome.py", line 622, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File "/opt/salome/appli_V8_2_0/bin/salome/runSalome.py", line 419, in startSalome
clt=orbmodule.client(args)
File "/opt/salome/Salome-V8_2_0-univ/modules/KERNEL_V8_2_0/bin/salome/orbmodule.py", line 47, in __init__
self.initNS(args or {})
File "/opt/salome/Salome-V8_2_0-univ/modules/KERNEL_V8_2_0/bin/salome/orbmodule.py", line 86, in initNS
sys.exit(1)
SystemExit: 1
--- Error during Salome launch ---
But we'll see how it goes.
I really appreciate all of the help from everyone, if I'm successful I'll update this thread.
Wink
Offline
I'd already tried building Salome with 2.7.13 and it "worked", i.e. I was able to successfully compile 2.7.13 sources while building Salome. But then it wouldn't compile qt 5.6.1 which I'm guessing is because Arch is on qt 5.9.1 so it seems I'm in "dependency hell" on all paths
Was that using the PKGBUILD's from AUR?
Offline
No, I'll try that too, but it was 7.8.0 IIRC and I wanted to use 8.2.0 but I'll try it and report back.
Offline
I investigated Salome in AUR. The author provides some notes but it was an older version so it seemed more work than was worth it.
I also made a progress after watching this video. I downloaded salome-meca 2016 from the code_aster site and was able to run it using a virtualenv2 python environment and didn’t have to modify the /usr/bin/python link as suggested in the video. One note of caution, I tried to run the tests, of which the first test of 7602 tests, salomeLauncher, fails. The next 240 ish tests passed, but then 99% of the subsequent 2365 tests that ran for the next 10 hours failed, so I stopped it.
Finally, I also got docker image to work with some help from the author as indicated in my comments in the docker page.
Again, thanks for the help,
Wink Saville
Offline
Simple Python version managemen
However the proper solution is to fix the crappy code so that it works on a up to date python version.
Last edited by Mr.Elendig (2017-07-28 23:35:23)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline