New v2 installation on debian lenny 64bit

[Sébastien Avila]

Hi,
i am trying to install Code saturne v2.
To do that, I created some folders.In /home/, I first created a folder named saturne. Then, in /home/saturne/, I created the folders: Enveloppe Install Interface Noyau and src.
I downloaded and put the folder ecs-2.0.1/ in Enveloppe/
I downloaded and put the folder ncs-2.0.1/ in Noyau/
I downloaded and put the folder ics-1.3.3/ in Interface/
I downloaded and put the folders bft-1.1.4, mei-1.0.2 and fvm-0.15.2 in src/
I downloaded and put the folder installateur 1.3.3 in Install/

In the Install/ folder, I edited the setup file, like this:
nom_arch Linux_x86_64
compC   gcc
compF   gfortran
language   FR
python   /usr   python   yes   no
blas   None   atlas-3.8.2   no   no
metis   None   metis-4.0   no   no
mpi   None   openmpi-1.2.8   no   no
cgns   None   cgns-2.5.3   no   no
hdf   None   hdf5-1.6.7   no   no
med   None   med-2.3.4   no   no
bft   /home/saturne/opt/bft-1.1.4/arch/Linux_x86_64   bft-1.1.4   yes   yes
fvm   /home/saturne/opt/fvm-0.15.2/arch/Linux_x86_64   fvm-0.15.2   yes   yes
ecs   /home/saturne/Enveloppe/ecs-2.0.1/arch/Linux_x86_64   ecs-2.0.1   yes   yes
ics   /home/saturne/Interface/ics-1.3.3   ics-1.3.3   yes   yes
ncs   /home/saturne/Noyau/ncs-2.0.1   ncs-2.0.1   yes   yes
syr_cs   None   syr_cs-2.1.1   no   no
syrthes   None   syrthes3.4.2   no   no

At last, I launched the script ./install_saturne.py
After a moment, I get the following error:
Installation of ncs-2.0.1 on architecture Linux_x86_64

Error : opening /home/saturne/Noyau/ncs-2.0.1/bin/macros_Linux_x86_64.mk

I looked into the folder /home/saturne/Noyau/ncs-2.0.1/bin/, and effectively, there is no file named macros_linux_x86_64.mk
What can I do to solve this?
Many thanks in advance.
Sébastien

[Yvan Fournier]

Hello,

It seems that the installer posted for version 2.0 is that of 1.3, so we'll try to have that corrected.

Code_Saturne 2.0's install is completely different from that of 1.3, as all packages now use autoconf/automake/libtool, so the installer from 1.3 won't work.

I'll check with David for the latest version of the installer, but in the meantime, here is an installer script I just updated from the one in ncs-2.0.1/extras/installer.

I cannot test it from here due to a proxy, so good luck (i may test it and correct it this evening)

Best regards,

  Yvan

[Sébastien Avila]

Thanks
I will try it and keep you in touch.

[Sébastien Avila]

OK, it was a pain but I get something.

I edited the install_saturne.py in order to change the version of the different library which have to be taken into account (bfm, ecs, ...). Then I unzip them and tgz them (why can't one directly download a tgz instead of a zip file?)

Then I put all the installer files and the tgz libraries in the same folder and run the install (without neither cgns neither mpi, i do not need them for the moment).

During the compilation of the mei libray, I get the following error (see log in attachment). Do you have any idea?

Many thanks again!

sébastien  

[Yvan Fournier]

Hello,

The issue with zip files is that the main EDF web site policy does not accept .gz files. A copy of the libraries in tar.gz format will also be placed on code-saturne.info, but in the meantime, the code-saturne.org website is the only place to get them. Still, the install script I posted should be able to download and uncompress the files automatically.

Which library versions did you have to modify ?

It seems you are missing Python developpement headers (required for SWIG), as Python.h is not found. If you are running on a standard Linux distribution, install "python-dev" if possible. Otherwise, try to compile Code_Saturne without MEI support.

Best regards,

   Yvan fournier

[Sébastien Avila]

My fault. I used the install-saturne.py from ncs-2.0.1/extras/installer instead of the one you posted previously...

Whatever, I just installed python-dev and MEI is compiling well. And now, I have got a compilation error for ncs.

Here are the last line of the log file:  

mv -f .deps/syr_defs.Tpo .deps/syr_defs.Plo
/bin/sh ../libtool  --tag=CC   --mode=link gcc  -std=c99 -funsigned-char -pedantic -W -Wall -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Wunused -Wfloat-equal  -no-undefined -version-info 0:0:0 -Wl,-export-dynamic  -O -o libsyrcs.la -rpath /home/cs-2.0/lib syr_comm.lo syr_coupling.lo syr_cs.lo syr_defs.lo  -ldl
libtool: link: gcc -shared  -fPIC -DPIC  .libs/syr_comm.o .libs/syr_coupling.o .libs/syr_cs.o .libs/syr_defs.o   -ldl  -Wl,-export-dynamic -O   -Wl,-soname -Wl,libsyrcs.so.0 -o .libs/libsyrcs.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libsyrcs.so.0" && ln -s "libsyrcs.so.0.0.0" "libsyrcs.so.0")
libtool: link: (cd ".libs" && rm -f "libsyrcs.so" && ln -s "libsyrcs.so.0.0.0" "libsyrcs.so")
libtool: link: ar cru .libs/libsyrcs.a  syr_comm.o syr_coupling.o syr_cs.o syr_defs.o
libtool: link: ranlib .libs/libsyrcs.a
libtool: link: ( cd ".libs" && rm -f "libsyrcs.la" && ln -s "../libsyrcs.la" "libsyrcs.la" )
make[2]: quittant le répertoire « /home/saturne/ncs-2.0.1.build/libsyrcs »
Making all in po
make[2]: entrant dans le répertoire « /home/saturne/ncs-2.0.1.build/po »
test ! -f /home/saturne/ncs-2.0.1/po/ncs.pot || \
test -z "/home/saturne/ncs-2.0.1/po/fr.gmo" || make /home/saturne/ncs-2.0.1/po/fr.gmo make[3]: entrant dans le répertoire « /home/saturne/ncs-2.0.1.build/po »
cd /home/saturne/ncs-2.0.1/po && rm -f fr.gmo && : -c --statistics --verbose -o fr.gmo fr.po
mv: ne peut évaluer `t-fr.gmo': Aucun fichier ou répertoire de ce type
make[3]: *** [/home/saturne/ncs-2.0.1/po/fr.gmo] Erreur 1
make[3]: quittant le répertoire « /home/saturne/ncs-2.0.1.build/po »
make[2]: *** [stamp-po] Erreur 2
make[2]: quittant le répertoire « /home/saturne/ncs-2.0.1.build/po »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/saturne/ncs-2.0.1.build »
make: *** [all] Erreur 2

A new missed library? (by the way, how did you managed to know it was a python-dev issue...?)

Thanks

Sébastien

[Sébastien Avila]

It is resolved, I missed again some libraries.

Thanks for the help!

Let's go test it!

[Yvan Fournier]

Hello,

Good. In the first case, I guessed that you were missing python-dev because there was a:

mei_wrap.c:124:20: error: Python.h: Aucun fichier ou répertoire de ce type

message about 3/4ths of your log.

I compared you latest message with the Makefile in po, and it seems that msgfmt was missing, and that is part of gettext. A workaround would be to add the --disable-nls to Code_Saturne's configure, but this is the first time we encounter this issue (gettext is probably installed on the vast majority of machines), so in the future, we should test for gettext, or build the .gmo file when building the distribution (not when installing).

Thanks for the feedback.

Best regards,

  Yvan

[Martin Isack]

Hello,
just one question regarding the zip file problem. Wouldn’t it be possible to to put the files in a tar or tar.gz archive first and zip the archive afterwards for uploading to the EDF web site?
Regards,
Martin

[Laurent Malod-Panisset]

Hi
 
Just a small account of using the installer.tgz on an Ubuntu LTS release
1) zip / tgz
For some reasons, the script didn't work well: it was ok with the tgz archives but couldn't deal with the zip files, thinking it was tgz files
I just commented some parts of the "extract" function and relaunched the install, which went almost fine afterward
 
2) Archive name
archive="ecs-2011.zip" not correct. I just changed to ecs-201.zip as far as i recall
 
3) One issue with a missing librairy: gettext after that, but easily solved
 
So, thanks for the installer an have a nice day