Feedback on "Universal binaries for Linux" packagings

Hello,

Please report here all issues related to the "Universal binaries for Linux" packagings.

Don't forget to specify your Linux distribution and architecture.

Of curse, we cannot test all Linux distributions, then if you have no trouble with these packagings on you specific distribution, please let us know too.

The only prerequisite for these packagings are a python interpreter.

To remind you how to run :

To run this versions, extract the archive and execute runSalome script.

These packagings are known to work on distributions like Ubuntu, Suse,RHEL, ....

Best regards,

Nicolas

Hi Nicolas,

are OK !

E.A.

Hi Nicolas,

Works fine in Slackware64 13, although there are some hacks to be performed...:

libg2c must be installed previously, and a symlink in LD_LIBRARY_PATH called libgfortan.so.1 pointing to /usr/lib64/libgfortran.so.3 must be created.

And the installer is 32bit executable...  had to install in batch mode...  ~

BRGDS

Alex

Previously Alex wrote:

Hi Nicolas,

Works fine in Slackware64 13, although there are some hacks to be performed...:

libg2c must be installed previously, and a symlink in LD_LIBRARY_PATH called libgfortan.so.1 pointing to /usr/lib64/libgfortran.so.3 must be created.

And the installer is 32bit executable...  had to install in batch mode...  ~

 

BRGDS

 

Alex

Hello Alex,

The 2 libraries libg2c and libgfortran are provided in the Debian layer (in directory [INSTALLROOT]/Salome_5.1.3/SALOME5/Prerequis/etchForSalome/lib), thus it should not be needed in the system.

What do you call installer ? There is no installer, just a tgz archive file do decompress. Then the "launcher" runSalome is a shell script.

Gilles

Unpackaging it in my user/home folder on Ubuntu 9.10-64 Bit, starts!
(where the installer had failed on the exact same system)

So far, I have tested Post-Pro.

My current system has been tweaked with instructions from:
http://wwiki.free.fr/index.php?post/2009/12/31/Install-Salome-513-on-Ubuntu-910-64-bit-Karmic

Booting yields this, which I hope is nothing serious:

CHECK /home/brenda
Searching for free port for the SALOME Naming Service: 2810 - Ok
Configure parser: Warning : could not find user configuration file
runSalome running on brenda-lpl
Configure parser: Warning : could not find user configuration file
Searching for a free port for naming service: 2810 - OK
Searching Naming Service + found in 0.1 seconds
Searching /Containers/brenda-lpl/FactoryServerPy in Naming Service ++++++FactBatchManager of type 'eSGE' inserted into catalog
FactBatchManager of type 'ePBS' inserted into catalog
FactBatchManager of type 'SH' inserted into catalog
FactBatchManager of type 'RSH' inserted into catalog
FactBatchManager of type 'SSH' inserted into catalog
+FactBatchManager of type 'eSGE' inserted into catalog
FactBatchManager of type 'ePBS' inserted into catalog
FactBatchManager of type 'SH' inserted into catalog
FactBatchManager of type 'RSH' inserted into catalog
FactBatchManager of type 'SSH' inserted into catalog
 found in 3.5 seconds
Searching /Kernel/Session in Naming Service ++++++ found in 3.0 seconds
Start SALOME, elapsed time :   6.9 seconds
additional external python interpreters:  0
>>> ****************************************************************
*    Warning: DSCCODE GUI resources are not found.
*    DSCCODE GUI will not be available.
****************************************************************

It is quite nice to see Salome 5.1.3 on Linux!

Thank you very much indeed!

[Theme note: using the RBG values: 143, 95, 74 will make the highlight blend in with the default Ubuntu 9.10 theme. The tooltip background can be changed to RGB: 245, 245, 181. I also changed the font to San Serif]

Tested on Mandriva 2010.0 64bit (on the same workstation Salome 5.1.3 was already installed, by means of the mandriva_2008 installer):

All is working as expectd, just this warning at boot:

****************************************************************
*    Warning: DSCCODE GUI resources are not found.
*    DSCCODE GUI will not be available.
****************************************************************

On Mandriva 2010 64bit, a little problem:

The program starts correctly by command line, but it does not start if I create a launcher in the gnome interface. The way to fix this is to modify the launcher with the instruction "execute in a terminal", but in this way I have a terminal window for all the time that I need to use Salome, and when I shut down Salome by the "exit" menu, the terminal remains opened and I have to kill it by hitting CRTL+D.

The warning about DSCCODE GUI resources are not found is normal: it means that DSCCODE module does not have any GUI. But as this module is meant to be used in a YACS schema, it does not need a GUI.

Concerning the launcher, you did it the good way.  Having a terminal opened during the Salome session does not look as a problem to me. At EDF site, it is the current behaviour.

Regards,
Gilles

Previously DAVID Gilles wrote:

 

Concerning the launcher, you did it the good way.  Having a terminal opened during the Salome session does not look as a problem to me. At EDF site, it is the current behaviour.

Ok, it just a little bit annoying to have a useless more window opened.

The "normal" installation of Salome with the installation wizard of Salome 5.1.3 does not suffer of this problem, I created a simple script:

#!/bin/bash
source /opt/salome_5.1.3/env_products.sh
source /opt/salome_5.1.3/KERNEL_5.1.3/salome.sh
/opt/salome_5.1.3/KERNEL_5.1.3/bin/salome/runSalome

and when I call it by means of a gnome-launcher, Salome starts without the need to execute it in a terminal.


BTW, thank you for this new package!

In runSalome, try to replace :

${KERNEL_ROOT_DIR}/bin/salome/envSalome.py python -i ${KERNEL_ROOT_DIR}/bin/salome/runSalome.py $*

by :

${KERNEL_ROOT_DIR}/bin/salome/envSalome.py python ${KERNEL_ROOT_DIR}/bin/salome/runSalome.py $*

(Note the remove of "-i" option)

And comment or remove the following line:

python ${KERNEL_ROOT_DIR}/bin/salome/killSalomeWithPort.py ${NSPORT}

.

Previously DAVID Gilles wrote:

 

Then create and test your launcher again

.

It works perfectly now, after executing your modifications!

thank you very much!

Almost work on Mandriva 2010.0 32 bits : everything OK, except Geometry module

Get a 'SIGSEV segmentation violation detected. Address 30' message on launching this module.

I posted all details in the 'SIGSEV' specific topic, but it concerns also this topic, as I use the Universal Binary Package....

Previously DAVID Gilles wrote:

Previously Alex wrote:

Hi Nicolas,

Works fine in Slackware64 13, although there are some hacks to be performed...:

libg2c must be installed previously, and a symlink in LD_LIBRARY_PATH called libgfortan.so.1 pointing to /usr/lib64/libgfortran.so.3 must be created.

And the installer is 32bit executable...  had to install in batch mode...  ~

 

BRGDS

 

Alex

Hello Alex,

The 2 libraries libg2c and libgfortran are provided in the Debian layer (in directory [INSTALLROOT]/Salome_5.1.3/SALOME5/Prerequis/etchForSalome/lib), thus it should not be needed in the system.

What do you call installer ? There is no installer, just a tgz archive file do decompress. Then the "launcher" runSalome is a shell script.

Gilles

Hi Giles,

I mean that the GUI mode does not work in 64bits slackware, yet in multilib (mixed 32 and 64 bit architecture ) it works...  I guess it must have been compiled for 32 only...

Yet it install allright if one installs in batch mode.. 

One more question, a bit off topic, IMHO, but here it goes :

I wish to install the Med-2.3.6.tgz that ships with Code Aster, there are a few applications from EDF that have mesh conversion utilities that call for med libraries, like convert2syrthes, and a mesh conversion application posted in this forum by user Bernhardi; it converts the meshes created in Salome to the Calculix format.

I do not get to have the med_config.h installed in /usr/local/include, however I compile med-2.3.6 successfully...  running ./configure --help yelds me no hint neither...

Do you have any Idea how can I get med_config.h to /usr/local/include as well as its symbols to be compiled into the library objects...?

BRGDS

Alex 

.

Previously Francois Cauneau wrote:

Almost work on Mandriva 2010.0 32 bits : everything OK, except Geometry module

 

Get a 'SIGSEV segmentation violation detected. Address 30' message on launching this module.

I posted all details in the 'SIGSEV' specific topic, but it concerns also this topic, as I use the Universal Binary Package....

 

 

Checked : Universal Binary for Linux 32bits works perfectly on my Mandriva 2010.0

The bug was in fact concerning integrated version 4.1.3 inside the Salome-Meca package. Nothing to do here.

Francois

Hi,

I confirm it works perfectly on both kubuntu Karmic 9.10 32 and 64 bits.

I've installed it on 32 and 64 bits servers of my laboratory (ubuntu/kubuntu Karmic 9.10), and on 8 pc on a classroom with code aster (kubuntu Karmic 9.10 64bits).

Very good work!!!!!

Bye

Hi,

I've tested it on Fedora 11 64bits. Works well !

Good job

I have tested the package on Mandriva 2010-32bit too and it works well. The only issue is related to some problems in the geometry module, due to the fact the the old graphic board is not supported by the current propietary video driver (ATI X700M).

Is it possible to start Salome in a sort of "safe mode", even accepting slow performances, to avoid all artefacts on video?

Hello Cacciatorino,

Graphic cards and graphic drivers can really be an issue in Salome. 

Today, Salome does not have any "safe mode". It works fine on recent graphic cards but old ones can be problematic.

I'm afraid that it won't be changed in a close future.

Gilles

Previously DAVID Gilles wrote:

Hello Cacciatorino,

Graphic cards and graphic drivers can really be an issue in Salome. 

Today, Salome does not have any "safe mode". It works fine on recent graphic cards but old ones can be problematic.

I'm afraid that it won't be changed in a close future.

Gilles

Hello Gilles,

thank you for answering!

Imho, the problem is more related to Linux than Salome: the support for "old" hardware (we are speaking of a 3 years old laptop) ceases too early if compared to other operating systems.

A partial solution exists: go to the control panel of Mandriva and remove the 3d-acceleration from the graphic card driver. The problem is that this affects the whole system, not Salome only.

Hello Cacciatorino,

Have you look around configuration of DRI (http://dri.freedesktop.org/wiki/ConfigurationInfrastructure), it seems that you can deactivate 3d acceleration per software.

However ,the page seems pretty old, it seems to work only on open-source drivers and I did manage to let it work on Fedora (in 5 minutes). But it can help...

Matthieu

Good evening gents,

I am curently under ubuntu 9.04 64, I don't understand where we have to extract and install the binairies, or /user/home like Brenda EM did, or in /usr/share, or in /opt/, or somewhere else....

And why have you chosen this, where can it works easily, what are the advantages and drawback of each ?

My planned application is a calculation server with several users.

@Benjamin BONIFACE

How have you created the links between salome and code aster in servers, please?

Thanks to all.

Gwen

Hello Gwen,

The binaries provided by "universal" archives are not meant to be installed anywhere. Just uncompress the archive anywhere you want and run the script runSalome to launchh the application.

It is an easy and fast way to have a ready-to-use Salome application working on most linux distribution.

The difference with the other packaging (Install Wizard) is that it does not permit to recompile Salome from the sources, neither to make developments based on it. It is just a runtime packaging.

Hope this answers to your questions.

Regards,

Gilles

Sorry I wanted to say: "The binaries provided by "universal" archives are meant to be installed anywhere."

Good mornings gents,

Many thanks Gilles, i will try to install this week.

And to do a code aster case.

Regards

Gwen

Attention: Salome 5.1.3 provided here does not come with Code Aster.

This is done by Salome-Meca but current version includes Salome version 4.1.4.

The next version of Salome-Meca will include a version 5.x of Salome.

Previously DAVID Gilles wrote:

Attention: Salome 5.1.3 provided here does not come with Code Aster.

This is done by Salome-Meca but current version includes Salome version 4.1.4.

The next version of Salome-Meca will include a version 5.x of Salome.

I know you're working hard on the Meca version, but do you have a time frame for it? Just so we have something to look forward to

Tested runtime of Salomé on Ubuntu Karmic 64bit, works great - I really think it's a great way to release it.

Well I'm not part of the Salome-Meca team. They are different people than those who develop Salome itself.

Thus it is difficult for me to give you any time frame. I guess it will be during the year but I really don't know when.

I just wanted to say thank you again, for making the 5.x universal binaries : )

I'm running them on Ubuntu 9.10-64.

So far, I have not had any problems.

The interface is much better, and better looking than 4.x.

[I've got Aster going on Ubuntu 64; and I'm working on leaning how to run externally from Salome

http://www.code-aster.org/forum2/viewtopic.php?pid=19445#p19445 ]

I know that I was a little coarse about the installers, but the universal binaries work.

Previously Cacciatorino wrote:

On Mandriva 2010 64bit, a little problem:

 The program starts correctly by command line, but it does not start if I create a launcher in the gnome interface. The way to fix this is to modify the launcher with the instruction "execute in a terminal", but in this way I have a terminal window for all the time that I need to use Salome, and when I shut down Salome by the "exit" menu, the terminal remains opened and I have to kill it by hitting CRTL+D.

Hello cacciatorino,

This is the command line for my gnome launcher:

[code]

xterm -e "source /opt/salome_5.1.3/env_products.sh; runSalome; exit"

[/code]

It works for me.  The xterm window closes shortly after Salome 5.1.3 is launched on my Ubuntu 9.04 Jaunty 64bit.

Regards,

JMB

Hello everybody, I tried to use salome for the first time, and it failed. My distrib is Arch Linux, on x86-64 architecture.

It seems that the libc is not the same that the one with which you compiled salome or something like that:

python: relocation error: /home/vinvin/Salome_5.1.3/SALOME5/V5_1_3/../Prerequis/etchForSalome/lib/libc.so.6: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference

several times.

Any help? Thanks in advance!

Regards, Vincent