Page 2 of 2

Re: Problem with libsaturne.so.0

Posted: Wed Jun 09, 2010 4:28 pm
by Chebli Rezki
Hello;
I have same problem but I doesn't find solution.
/usr/local/bin/cs_preprocess: error while loading shared libraries: libbft.so.1: cannot open shared object file: No such file or directory
knowing that libbft.so.1 file is present in /usr/local/lib.
Regards.
Rezki.

Re: Problem with libsaturne.so.0

Posted: Wed Jun 09, 2010 5:32 pm
by Chebli Rezki
when I re-ran "make install" for the the Code_Saturne kernel (ncs), I had this error

/usr/bin/ld: cannot find -lfvm_coupl
collect2: ld returned 1 exit status

make[3]: *** [cs_solver] Erreur 1
make[3]: quittant le répertoire « /home/rezki/saturne/ncs-2.0.0-rc1/src/apps »
make[2]: *** [all-recursive] Erreur 1
make[2]: quittant le répertoire « /home/rezki/saturne/ncs-2.0.0-rc1/src »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/rezki/saturne/ncs-2.0.0-rc1 »
make: *** [all] Erreur 2

Regards

Rezki

Re: Problem with libsaturne.so.0

Posted: Wed Jun 09, 2010 11:14 pm
by David Monfort
Hello Rezki,

The solution to your problem is a couple of post before yours... here is an excerpt of Norbert's post:
The problem has been solved by adding /usr/local/lib to /etc/ld.so.conf then runing ldconfig.
This should solve both of your issues. If that's not the case, tell us. Another solution is also given a few post before (based on LD_LIBRARY_PATH).

David

Re: Problem with libsaturne.so.0

Posted: Fri Jun 11, 2010 11:50 am
by Chebli Rezki
Hello David,
I think that it works.
I want to install CFDSTUDY to coupled SALOME_5.1.3 with Saturne2.0-rc1, that is recommended for cavitation flows ?
Thank you very much.
Rezki

Re: Problem with libsaturne.so.0

Posted: Fri Jun 11, 2010 10:01 pm
by David Monfort
Hello Rezki,
Actually, you don't need to have CFDSTUDY installed in order to develop a method for flows with cavitation. CFDSTUDY is only a plug-in to integrate Code_Saturne graphical interface within the SALOME platform.
Furthermore, this module can sometimes be difficult to install... We need to improve that point.
David

Re: Problem with libsaturne.so.0

Posted: Tue Jun 15, 2010 10:43 am
by Chebli Rezki
Thank you for this information David,
For this application, I am interested by the use of open source mesh generator, how you judge SALOME_5.1.3 ?
can you compare it with Start CCM+ which I can have license ?
Regards.
Rezki.

Re: Problem with libsaturne.so.0

Posted: Thu Jun 17, 2010 12:56 am
by David Monfort
Hi Rezki,
It really depends on two factors: the geometry you want to mesh and your ability to use both tools. I think you will have to try by yourself, but keep in mind that you are trying to compare a free and open-source tool with a paying-licensed one... I'm not saying here that one is better than another!
You also need to know that Code_Saturne preprocessor can only read Star-CCM+ meshes if it is linked against the libccmio library (normally available on request via the CD-Adapco support, or maybe available on download on the ViSiT website).
If you go for the SALOME platform, be sure to read through their forum (see http://www.salome-platform.org) as we won't be of much help on these topics.
David

Re: Problem with libsaturne.so.0

Posted: Thu Jun 17, 2010 1:29 pm
by Chebli Rezki
Hi David,
OK, thank you very much for these informations.
For the moment I use SALOME and I try to create my geometry (Hydrofoil).
Thank you again.
Best regards.
Rezki

Re: Problem with libsaturne.so.0

Posted: Thu Apr 26, 2012 10:23 am
by Alexandre Lebouvier
Hi everyone,
 
I am desintering that old post because I have a similar problem. I use code_saturne 2.0.2 that I have installed on Ubuntu 11 with the command apt-get. The installation seems fine. I have tested one case with the GUI and it works fine. But, when I launch a typical plasma case I have without GUI, which one I use usually to test the performance (so this case works fine on other machines), I get a similar error :
 
 Reading file:        preprocessor_output
@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@
@ @@ WARNING:    stop in data input
@    =======
@     The user subroutine 'usipph' must be completed
@       in file usini1.f90
@
@  The calculation will not be run.
@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@
 
 
Call stack:
   1: 0xe4c6f9     <cs_exit+0x99>                   (libsaturne.so.0)
   2: 0xe4cead     <csexit_+0x1d>                   (libsaturne.so.0)
   3: 0x105a59e    <usipph_+0x92>                   (libsaturne.so.0)
   4: 0xf9c0c1     <iniusi_+0x119>                  (libsaturne.so.0)
   5: 0xf9bc18     <initi1_+0x28>                   (libsaturne.so.0)
   6: 0xe0ed83     <cs_run+0xa3>                    (libsaturne.so.0)
   7: 0xe0ebfc     <main+0x24c>                     (libsaturne.so.0)
   8: 0xaa1113     <__libc_start_main+0xf3>         (libc.so.6)
   9: 0x80499c1    <>                               (cs_solver)
End of stack
 
I had a look at this post : https://code-saturne.info/products/code-saturne/forums/general-usage/915591566
but my usini1.f90 file is present, and i don't have PARAM argument as I don't use the GUI.
 
So, I tried the advice given below. I add "export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH" to my .bashrc. The point is that my libsaturne.so.0 file is not present in /usr/local/lib but in /usr/lib. Anyway I created a symbolic link of this library in the /usr/local/lib folder, but it makes no different at the end, i got the same error message. I also tried to export directly /usr/lib.
I also added /usr/lib/ and /usr/local/lib/ to the /etc/ld.so.conf file and then run ldconfig with root permission, without success.
 
Any other idea?
 
Best Regards,
 
Alexandre
 

Re: Problem with libsaturne.so.0

Posted: Mon Apr 30, 2012 4:17 pm
by Yvan Fournier
Hello,

This seems to be a packaging issue, and I was able to reproduce it, but not solve it.

Another user reported this problem as having dissapeared when switching to the Code_Saturne 2.1 package, so I would recommend either trying this, or using an unpackaged version of the code (version 2.0.5 or 2.2.1 depending if you prefer more validation or a more up-to-date version).

Best regards,

  Yvan