Welcome to the forums. Please post in English or French.

You are not logged in.

#1 2018-10-24 08:31:48

mareitioaurtena
Member
Registered: 2018-10-24
Posts: 1

Problem when installing Salome-Meca 2017 (and 2018) in Ubuntu

Hello,

I tried to install Salome-Meca (v2017 and also v2018 once I saw this problem, but the result was the same) on my Linux PC (Ubuntu) and I got this issue:

======================================================
Self Extracting salome_meca V2018.0.1_public Installer
======================================================

Enter the salome_meca install directory [default=/home/ubik/salome_meca] :
salome_meca is in English, do you want to be in French ? [y/N] : n
Installation of salome_meca V2018.0.1_public in /home/ubik/salome_meca/V2018.0.1_public ...
Verifying archive integrity...
All good.
Done                                                                                                                                                                                                             
./create_appli.sh: line 108: /salome_prerequisites.sh: No such file or directory
./create_appli.sh: line 109: /salome_modules.sh: No such file or directory
Creating salome_meca application in /home/ubik/salome_meca/appli_V2018.0.1_public ...
sed: can't read /.config_appli_template.xml: No such file or directory
grep: salome_context.cfg: No such file or directory
salome_meca post-installation ...
./create_appli.sh: line 263: python: command not found
./create_appli.sh: line 287: ./salome_post_install.py: No such file or directory
The salome_meca application was successfully created.
To run the application:
$ /home/ubik/salome_meca/appli_V2018.0.1_public/salome
Adjusting wishexecutable /home/ubik/salome_meca/V2018.0.1_public/tools/Code_aster_frontend-201801/etc/codeaster/profile.sh
Initialize terminal and editor for Code_aster
Final configuration
ubik@2106-126:~$ /home/ubik/salome_meca/appli_V2018.0.1_public/salome
bash: /home/ubik/salome_meca/appli_V2018.0.1_public/salome: No such file or directory
ubik@2106-126:~$ /home/ubik/salome_meca/appli_V2018.0.1_public/salome

----------

I saw on the forum that many people encountered this issue and it is likely due to two python versions existing on the PC (2.7 which I already installed and default python3 for Ubuntu). Then I tried what Thomas de Soza mentioned on another post for this topic (Try editing the "*.run" file with a command line text editor and change the "python" calls (at least three) to "python2").

Then I found this other issue:


===============================================
Self Extracting salome_meca V2017.0.2 Installer
===============================================

Enter the salome_meca install directory [default=/home/ubik/salome_meca] :
The directory /home/ubik/salome_meca/V2017.0.2 already exists, install anyway ? [y/N] y
salome_meca is in English, do you want to be in French ? [y/N] : n
Installation of salome_meca V2017.0.2 in /home/ubik/salome_meca/V2017.0.2 ...
Verifying archive integrity...
Error in MD5 checksums: 5b620e37b5294dfe1db9a93de8a37e27 is different from 33e17e2fb7b91baf053d4f97bf489013


-----

So now my *.run file is most likely corrupted and cannot be installed.

Anyone facing the same problems?

Thank you!

Maialen

Offline

#2 2018-10-25 09:02:09

k_zurawski
Member
From: Gdansk (Poland)
Registered: 2010-03-13
Posts: 167

Re: Problem when installing Salome-Meca 2017 (and 2018) in Ubuntu

Since the integrity check went well it should be ok, but I still have doubts if you downloaded instalation files without error. I'm trying for at least 10th time to download salome-meca 2018 and still have network error. Have you checked md5?

Last edited by k_zurawski (2018-10-25 09:02:42)


regards,
Krzysztof

Offline

#3 2018-11-03 14:00:11

Thomas DE SOZA
Guru
From: EDF
Registered: 2007-11-23
Posts: 3,066

Re: Problem when installing Salome-Meca 2017 (and 2018) in Ubuntu

Hello,

Th problem is that the default python in your system points to Python3.
Try to follow the advices I gave in another post (not the one telling to edit the .run file, this was a completely silly idea from my part but rather the one with the temporary modifications of the PATH* variables).

TdS

Offline