Как установить salome на ubuntu
Обновлено: 05.07.2024
ok . the installation crashes.
If you can , check the file downloaded . Open terminal go in the folder with the downloaded file ( not decompressed)
reinstall it and post the log of installion again.
Try the code in previous post. ( ./salome)
2 -check always that the prerequisites are installed ( with synaptic application).
gcc, g++, gfortran (or other compilers),
cmake,
python3,
python3-dev,
python3-numpy,
tk,
bison,
flex,
liblapack-dev, libblas-dev or libopenblas-dev,
libboost-python-dev (+ libboost-numpy-dev on ubuntu, boost-devel on centos) (for MFront),
zlib (named zlib1g-dev on debian/ubuntu).
Last edited by ing.nicola (2020-04-27 20:30:08)
zohir Member Registered: 2020-01-27 Posts: 10thank you i try..
sb1966 Member Registered: 2015-03-16 Posts: 2141) I have installed all the prerequisites as per
2) I have also installed python2-minimal (named so in 20.04LTS)
3) However, the same problem persists as given below:
./create_appli.sh: ligne 263: python : commande introuvable
4) One forum post said that in Xubuntu 20.04 some one has successfully installed. So I gave it a try, but the same problem arises there too.
5) I thought that it might be due to renaming python to python2 in 20.04. Hence created alias as follows:
in my .bashrc file.
6) However, this too did not solve the problem.
7) Tried to install everything as per the install script given for Ubuntu 18.04. at
But installation of libraries failed due to renaming many of them in Ubuntu 20.04/Xubuntu 20.04 repositories
8) Hoping and waiting eagerly to hear from the developers.
zohir Member Registered: 2020-01-27 Posts: 10 Jcm Member Registered: 2019-09-28 Posts: 11Good morning I have the same problem, I try to explain the procedure I followed:
I attached a .txt file with the log file of installation and a terminal message when I try to open Aster Study.
Jcm Member Registered: 2019-09-28 Posts: 11 Irvise Member Registered: 2019-12-07 Posts: 65The issue stems from libffi.so.6 not being found. The libffi library is a library that binds C code with other languages. In recent months, it had a mayor release and the older version is not compatible with the new one (that is why there is a .6 in it).
Therefore, in order to fix this issue you need to install libffi version 6. I have seen that the version of libffi shipped with 20.04 is version 7. I have searched for the possibility of a pre-packaged libffi6 for 20.04 but it seems no one has done it yet.
I believe you would be better off by building libffi yourself. Make sure you are using the 3.2 version and NOT THE 3.3 one.
Fernando Oleo Blanco
Jcm Member Registered: 2019-09-28 Posts: 11Thanks for your reply mr. Fernando.
If I compile the libffi version 6 (I downloaded libffi-3.2.1.tar.gz) can any issues with other applications occur?
Irvise Member Registered: 2019-12-07 Posts: 65There may be a problem if you move the header files, those may collide between versions. However, unless you are doing any development with ffi, everything should be fine.
Last edited by Irvise (2020-05-04 15:41:05)
hafid Member Registered: 2017-06-28 Posts: 17I have tried the following in and it works for me at least in manjaro 20.
Now I can launch asterstudy module.
Last edited by hafid (2020-05-04 15:45:06)
zohir Member Registered: 2020-01-27 Posts: 10Last edited by zohir (2020-05-07 04:45:39)
Jcm Member Registered: 2019-09-28 Posts: 11I confirm, I downloaded the "libffi6_3.2.1-9_amd64.deb" file from Download Page of Debian.
Now I can run Aster-Study
Regarding both python2 and libffi6 issues, the link below offers a solution under "Salome Meca 2019 (Success in 20.04)". Notice that one needs pyenv (addressed earlier in that same page).
sb1966 Member Registered: 2015-03-16 Posts: 214Installation of Salome-meca2019.0.3 in Xubuntu 20.04 was successful with these following minimalistic steps,
unlike the detailed python reinstall as described in the previous reply by ckrug. My steps are as follows:
2. Make sure also to install libopenblas-base.
3. Install the requisite qt5 pacakges and net-tools etc as described in forum post php?id=24470
4. install python2, named python2-minimal in ubuntu 20.04:
5. Install salome-meca following usual procedure.
5a. This will not create the application, but creates a script create_appl.sh.
6. edit the file to change "python" to "python2" in all its occurences (it occurs three times), as zohir described in one of his posts in this page.
6a. Then run this edited file in terminal:
.
This will install the application along with the desktop icon.
7. Install liffi6.3.2 as described earlier in this page.
viz.:
8. Create symbolic link of libffi.so.6 as follows:
9. remove or rename libstdc++.so* files in
This was essential to avoid opengl error in my case.
EDIT: This issue was also discussed in ___/forum2/viewtopic.php?id=24956
10. Now salome-meca-2019 can be invoked normally.
Hope this helps someone.
Last edited by sb1966 (2020-07-02 07:06:51)
Thanks for your posting - It was very helpful; I followed your steps to install on Ubuntu 20.4 and it went through well, but it has one Warning message at the end:
salome_meca post-installation .
Adjusting the file : /home/roger/salome_meca/appli_V2019.0.3_universal/SalomeApp.xml
Warning: the directory /home/roger/salome_meca/V2019.0.3_universal/modules/EUROPLEXUS_201901/lib/salome is in a path variable but does not exist
The salome_meca application was successfully created.
To run the application:
$ /home/roger/salome_meca/appli_V2019.0.3_universal/salome
Thanks for your posting - It was very helpful;
Thank you. It is nice to know that the post has become helpful to you. :-)
I can open the Salome application but I am not sure how serious this Warning will influence the program, and how to correct it. Please advise.
Hope this helps.
sb1966 Member Registered: 2015-03-16 Posts: 2142) The best way is to take a simple problem and run the study, then check your results, with analytical results (if available).
IMPORTANT: all these actions should NOT be made as root.
1-Install Wizard Process ( deprecated since 7.6.0 - Site Administrator )
Using the Install Wizard is the classical way to install Salome. In case of failure, the user can then try to use the universal binaries instead (see the next section).
1- First, go to the download page and select the file to download at the top of the page (under >> Binaries for officially supported Linux platforms (Installation Wizard):) according to your Linux distribution.
2- Once downloaded, open a Linux terminal/console and go where this file is (using the cd command).
3- Extract the file using the following command: (adapt the following command lines to your case)
tar -xvf InstallWizard_7.4.0_Ubuntu_13.10_64bit.tar.gz
4- Go inside the extracted folder and launch the runInstall file:
cd InstallWizard_7.4.0_Ubuntu_13.10_64bit
NB: If you get the error: bash: ./SOME_FILE: Permission denied, make this file executable by typing:
chmod +x ./SOME_FILE
5- The Install Wizard appears. Click on Next, letting the default setup. At a certain point, it can be necessary to select a "installation platform". In this case, select the only one which is available and go on.
Click on Start and wait for the end of the installation process.
At the end, you can maybe see an error message saying some libraries are absent. This does not mean that Salome won't work properly. You can note somewhere the name of these libraries in case you really need them in the future, then close the error message.
Click on Next and Finish.
6- To launch Salome, go inside the Salome folder:
source the env_product.sh file:
source env_products.sh
and execute the runSalome command:
7- To speed up the launch of Salome, the user can create a custom script. There are many ways to do it. Here is one possibility:
a) Create a bin folder in the home directory:
b) Create a script called salome and launching Salome:
/salome_7.4.0/env_products.sh\nrunSalome $*\nexit 0' >
c) Make it executable:
d) Declare that the bin folder contains terminal commands by adding its path to the $PATH variable in the .bashrc file which is read each time a new terminal is opened:
Then, the user can open a new terminal and launch Salome by typing directly:
2- Universal Binaries Process
If the Install Wizard method failed, the user can try to use universal binaries.
1- Download it from the the download page. (under >> Universal binaries for Linux:).
2- Once downloaded, open a Linux terminal and go were this file is (using the cd command).
3- Run the downloaded file:
4- Let the default values and press [Enter] until the installation begins.
5- To launch Salome, go to the Salome "appli" folder:
and execute the runAppli file:
6- To speed up the launch of Salome, you can create an alias in your .bashrc file:
Then, the user can open a new terminal and launch Salome by typing directly:
good job, that was needed!
may i had that creating a launching script
step 7 in 1- Install Wizard Process
applies as well to 2- Universal Binaries Process
may i say also that all these actions should NOT be made as root
as this makes a mess of the omniOrb permissions
(at least to my experience)
jean pierre aubry
You'r right. Nothing must be done as root !
I thought it was not necessary to mention it explicitly, but maybe it is.
All the best
I have a misfunctioning launcing salome:
(gconftool-2:5331): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running
(gconftool-2:5332): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running
runSalome running on linux.site
Searching for a free port for naming service: 2810 2811 2812 - OK
Searching Naming Service ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Failed to narrow the root naming context
Traceback (most recent call last):
File "/root/salome/appli/V7_4_0/bin/salome/runSalome.py", line 677, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File "/root/salome/appli/V7_4_0/bin/salome/runSalome.py", line 447, in startSalome
clt=orbmodule.client(args)
File "/root/salome/Salome-V7_4_0-LGPL-x86_64/modules/KERNEL_V7_4_0/bin/salome/orbmodule.py", line 47, in __init__
self.initNS(args or <>)
File "/root/salome/Salome-V7_4_0-LGPL-x86_64/modules/KERNEL_V7_4_0/bin/salome/orbmodule.py", line 86, in initNS
sys.exit(1)
SystemExit: 1
--- Error during Salome launch ---
How can I fix it ?
Traceback (most recent call last):
File "/root/salome/appli/V7_4_0/bin/salome/runSalome.py", line 677, in useSalome
As said at the top of the first post, Salome should not be installed as root.
Previously William Tougeron wrote:
Traceback (most recent call last):
File "/root/salome/appli/V7_4_0/bin/salome/runSalome.py", line 677, in useSalome
As said at the top of the first post, Salome should not be installed as root.
I have an other misfunctioning launcing salome:
runSalome running on linux.site
Searching for a free port for naming service: 2810 - OK
Searching Naming Service +Cannot open error log file: /tmp/logs/studio/omniNames_2810/omniNameErrors.log
usage: omniNames [-start [<port>]]
[-logdir <directory name>]
[-errlog <file name>]
Use -start option to start omniNames for the first time.
With no <port> argument, the standard default of 2809 is used.
Use -always in conjunction with -start to always start omniNames, regardless
of whether the log/data files already exist.
Use -logdir option to specify the directory where the log/data files are kept.
You can also set the environment variable OMNINAMES_LOGDIR to specify the
directory where the log/data files are kept.
Use -nohostname to suppress the inclusion of the hostname in the log files.
Use -errlog option to specify where standard error output is redirected.
Use -ignoreport option to ignore the port specification when determining
the end points to listen on, using -ORBendPoint arguments instead.
To publish a specific IP address to clients, use
Traceback (most recent call last):
File "/home/studio/salome/appli_V7_4_0/bin/salome/runSalome.py", line 677, in useSalome
clt = startSalome(args, modules_list, modules_root_dir)
File "/home/studio/salome/appli_V7_4_0/bin/salome/runSalome.py", line 447, in startSalome
File "/home/studio/salome/Salome-V7_4_0-LGPL-x86_64/modules/KERNEL_V7_4_0/bin/salome/orbmodule.py", line 47, in __init__
File "/home/studio/salome/Salome-V7_4_0-LGPL-x86_64/modules/KERNEL_V7_4_0/bin/salome/orbmodule.py", line 86, in initNS
--- Error during Salome launch ---studio@linux:
runSalome running on linux.site
Searching for a free port for naming service: 2810 - OK
Searching Naming Service +Cannot open error log file: /tmp/logs/studio/omniNames_2810/omniNameErrors.log
usage: omniNames [-start [<port>]]
[-logdir <directory name>]
[-errlog <file name>]
Use -start option to start omniNames for the first time.
With no <port> argument, the standard default of 2809 is used.
Use -always in conjunction with -start to always start omniNames, regardless
of whether the log/data files already exist.
Use -logdir option to specify the directory where the log/data files are kept.
You can also set the environment variable OMNINAMES_LOGDIR to specify the
directory where the log/data files are kept.
Use -nohostname to suppress the inclusion of the hostname in the log files.
I decided to initiate this thread because I havne't seem any about how or when it would be possible to install Salome on Ubuntu 20.04.
By now if you download the Universal Linux Binary, unpack and try to run it, it gives lots of error message. If someone had a different result or maybe could give some comment about the installing of Salome 9.5 on Ubuntu 20.04 I would appreciate.
Hi Thiago, can you share the error messages you report about with the universal linux binary ?
In case the experienced issues are about graphics libraries, you can use the embedded libraries which are shipped with the universal binary archives.
To link against these libraries, you need to uncomment this line in salome script file:
context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/system_dep/gl")
Sorry not posting the error message. I did what you suggested and now Salome 9.5 (Universal Linux Binary) its running nicely on my Ubuntu 20.04.1 LTS. Thank you.
I post bellow the errors messages I found and the solutions in the case of others find the same problems.
First error trying to run:
runSalome running on thiago-Inspiron-5557
Error when trying to access active network connections.
Traceback (most recent call last): .
SOLUTION: install net-tools - don't know why, just found in Google.
Second error trying to run:
runSalome running on thiago-Inspiron-5557
Searching for a free port for naming service: 2811 - OK
Searching Naming Service + found in 0.1 seconds
SALOME_Session_Server: error while loading shared libraries: libOpenGL.so.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
File "/home/thiago/SALOME-9.5.0/BINARIES-CO7/KERNEL/bin/salome/orbmodule.py", line 181, in waitNSPIDos.kill(thePID,0)
ProcessLookupError: [Errno 3] No such process
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/thiago/SALOME-9.5.0/BINARIES-CO7/KERNEL/bin/salome/runSalome.py", line 680, in useSalome
clt = startSalome(args, modules_list, modules_root_dir) File "/home/thiago/SALOME-9.5.0/BINARIES-CO7/KERNEL/bin/salome/runSalome.py", line 625, in startSalome session=clt.waitNSPID("/Kernel/Session",mySessionServ.PID,SALOME.Session)
File "/home/thiago/SALOME-9.5.0/BINARIES-CO7/KERNEL/bin/salome/orbmodule.py", line 183, in waitNSPID raise RuntimeError("Process %d for %s not found" % (thePID,theName))
RuntimeError: Process 9354 for /Kernel/Session not found
Searching /Kernel/Session in Naming Service
--- Error during Salome launch ---
SALOME platform is recently updated to version 5.1.1. This latest version ported the GUI onto the QT 4. For the old version 4.*, in which QT 3 is used, I suggest reading "Polishing GUI of older SALOME versions".
This poster introduces the installation procedure of SALOME 5.1.1. It is not difficult since the whole process is performed with help of a graphical interface and I already extracted the potential problems you might encounter in this article. All of the following instructions are tested on Ubuntu 9.04, and they are also compatible with the latest SALOME 5.1.3. For Ubuntu 9.10, you have to read "Installation of SALOME 5.1.2 on (K)Ubuntu 9.10 64 bit" for additional issues.
Okay, before start installing, we'd better fix two problems in advance.
1. Execute the following two commands
They replace "sh" with "bash", otherwise, there will be errors during the installation of SALOME, as shown in the following pictures.
2. An old version of the gfortran library libgfortran is necessary to enable the mesh module in SALOME. Execute the following commands to create a symbolic link so as to let a libgfortran.so.1 present. After the link is created, update the search path index.
(ldconfig is used to update /etc/ld.so.cache based on /etc/ld.so.conf, where the non-standard paths are added; updatedb is used to update the index database.)
An error like this will be encountered after the installation if there is no libgfortran existing. Matter of fact, it is also feasible to execute the above commands after the installation of SALOME.
Now you can launch the install script "runInstall" inside the directory InstallWizard_5.1.1_Debian_4.0/, which is obtained by extracting the suitable tar.gz package downloaded from the SALOME website. For Ubuntu 9.04, you can use Debian Etch version.
Run from the terminal:
Wait and see the GUI installation wizard, shown as
Following the wizard it is easy to install SALOME. It will take a while to finish the installation. You may see an warning like this after the finished installation. You just leave it. It doesn't matter.
Now you will have two directories "salome_5.1.1" and "salome_appli_5.1.1" at the installation location. Ship into salome_appli_5.1.1 and by running the script "runAppli" you could launch the SALOME software.
If encounter an error probably saying that the file .omniORB_%your username%_%your host name%_2810.cfg couldn't be found, you can manually create a sub-directory "USERS" under salome_appli_5.1.1 and try again.
Читайте также: