[MadsR]

It's odd, it should work on a non-altered Ubuntu. If you are updating stuff (libs) in the middle of a compile-error-recompile loop, you might get into trouble. Maybe you want to remove OpenFOAM-1.6.x completely and redo the git-part and then the ./Allwmake once more to be sure that linking is done correctly ? This might also be a complete waste of time :-/ but if you do not have anything else to try, it might be worth it.

/Mads

[ronaldo]

kate .bashrc &

[suitup]

Hey guys, i tried mads script and all works fine. I thought everything worked, but if I look into the make.log I see an error-msg in the end. I tried it twice, each try with the same results.

OpenFOAM/OpenFOAM-1.6.x/lib/linux64GccDPOpt \
-lspecie -lOpenFOAM -liberty -ldl -lm -o /home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/bin/linux64GccDPOpt/mixtureAdiabaticFlameT
make[2]: Verlasse Verzeichnis '/home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/utilities/thermophysical/mixtureAdiabaticFlameT'
make[1]: Verlasse Verzeichnis '/home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/utilities/thermophysical'
make: Das Target »application« wurde wegen Fehlern nicht aktualisiert.

in english:

OpenFOAM/OpenFOAM-1.6.x/lib/linux64GccDPOpt \
-lspecie-lOpenFOAM-liberty-ldl-lm-o / home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/bin/linux64GccDPOpt/mixtureAdiabaticFlameT
make [2]: Leaving directory `/ home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/utilities/thermophysical/mixtureAdiabaticFlameT '
make [1]: Leaving directory `/ home/fx/OpenFOAM/OpenFOAM-1.6.x/applications/utilities/thermophysical '
make: The target "application" was not updated due to errors.

After installing openssh-server, i could check the installtion with foamInstallionTest

sudo apt-get install openssh-server

The result was:

Checking basic setup...
-------------------------------------------------------------------------------
Shell:              bash
Host:               ubuntu
OS:                 Linux version 2.6.28-15-generic
-------------------------------------------------------------------------------


Checking main OpenFOAM env variables...
-------------------------------------------------------------------------------
Environment_variable Set_to_file_or_directory                Valid      Crit
-------------------------------------------------------------------------------
$WM_PROJECT_INST_DIR /home/fx/OpenFOAM                        yes       yes
$WM_PROJECT_USER_DIR /home/fx/OpenFOAM/fx-1.6.x               yes       no
$WM_THIRD_PARTY_DIR  /home/fx/OpenFOAM/ThirdParty-1.6.x       yes       yes
-------------------------------------------------------------------------------


Checking the OpenFOAM env variables set on the PATH...
-------------------------------------------------------------------------------
Environment_variable Set_to_file_or_directory                Valid Path Crit
-------------------------------------------------------------------------------
$WM_PROJECT_DIR      /home/fx/OpenFOAM/OpenFOAM-1.6.x         yes  yes  yes

$FOAM_APPBIN         ...6.x/applications/bin/linux64GccDPOpt  yes  yes  yes
$FOAM_SITE_APPBIN    ...nFOAM/site/1.6.x/bin/linux64GccDPOpt  no        no
$FOAM_USER_APPBIN    ...6.x/applications/bin/linux64GccDPOpt  yes  yes  no
$WM_DIR              /home/fx/OpenFOAM/OpenFOAM-1.6.x/wmake   yes  yes  yes
-------------------------------------------------------------------------------


Checking the OpenFOAM env variables set on the LD_LIBRARY_PATH...
-------------------------------------------------------------------------------
Environment_variable Set_to_file_or_directory                Valid Path Crit
-------------------------------------------------------------------------------
$FOAM_LIBBIN         ...M/OpenFOAM-1.6.x/lib/linux64GccDPOpt  yes  yes  yes
$FOAM_SITE_LIBBIN    ...nFOAM/site/1.6.x/lib/linux64GccDPOpt  no        no
$FOAM_USER_LIBBIN    ...penFOAM/fx-1.6.x/lib/linux64GccDPOpt  no        no
$MPI_ARCH_PATH       ...nmpi-1.3.3/platforms/linux64GccDPOpt  yes  yes  yes
-------------------------------------------------------------------------------


Third party software
-------------------------------------------------------------------------------
Software Version   Location 
-------------------------------------------------------------------------------
gcc      4.3.3     ...M/ThirdParty-1.6.x/gcc-4.3.3/platforms/linux64/bin/gcc
gzip     1.3.12    /bin/gzip                                                
tar      1.20      /bin/tar                                                 
icoFoam  1.6.x     ...penFOAM-1.6.x/applications/bin/linux64GccDPOpt/icoFoam
-------------------------------------------------------------------------------


Summary
-------------------------------------------------------------------------------
Base configuration ok.

Critical systems ok.


done.

no errors.

so i startet the cavity case with blockMesh and icoFoam, all worked without any problems, but after starting paraView i got the same massage like sarajags and the programm crashed after choosing OpenFoam-Files.

Originally Posted by sarajags_89

hi it took 3hrs .. When I start paraview from the cavity case file I get the following msg " A reader for cavity.Openfoam could not be found" please select one of the following.
1.protein data bank files
plot 3d files
digital elevation map files
stereo lithography
gaussian cube files
raw(binary files)
pop ocean files
AVS UCD binary /ASCII files
SESAME
comma -separated grid files
MFIX unstructured grid files
fluent case files
openfoam files
cosmology files

Which one do i select
!!!
thanks in adv

cheers

sarang

I red at another thread that i could use the command foamToVTK to convert the openfoam-files and load them into paraView. It worked. But by converting to vtk i miss the properties in the Object Inspector and cavity may not be able to be updated. Or can i use vtk without concern.



Sorry for my english, perhaps someone can help me


edit: I forgot announcing that i tried, without any changes:


cd $FOAM_UTILITIES/postProcessing/graphics/PV3FoamReader

./Allwclean
    ./Allwmake

edit2: i checked the size of make.log, it is 1,8 MB (1936494 Bytes), so maybe we could compare the size with yours, may be there are missing a few compiling files.

edit3: by starting paraView i get these massages in the terminal:

fx@ubuntu:~/OpenFOAM/OpenFOAM-1.6.x/tutorials/incompressible/icoFoam$ paraFoam -case cavity
created temporary 'cavity.OpenFOAM'
unknown chip id 0x9442, can't guess.
Read float past end of buffer
Read float past end of buffer
Read float past end of buffer
Read float past end of buffer

after choosing openfoam-file and crashing paraView these massages appear:

Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::_S_create
Aborted
fx@ubuntu:~/OpenFOAM/OpenFOAM-1.6.x/tutorials/incompressible/icoFoam$

i hope my last edit: i use ubuntu 9.04 64bit and mads 64bit-script

[MadsR]

Hi Suitup. heavy post you made there, but are you saying that after installing openssh, you got rid of the "make: The target "application" was not updated due to errors." -error??

/Mads

[suitup]

hi mad sry yes big post of me

i expressed me bad, i was not able to start foamInstallcheck, so i looked into some forumthreads and red that its able to start after installing openssh-server.

so openssh just solved the problem starting foarminstallcheck not more


so i ve just the issue that paraview has a bug.

I just postet the make.log, hoping that u can compare it to your log if you have the same last commands and to solve the issue, maybe there is a compiling probleme i dont know, i jsut started your script. But foaminstallcheck seems to say that everything is ok. so i wrote as summery that there appear no errors

[MadsR]

This just in :-) I've heard that running

apt-get install cmake

may help the "make: The target "application" was not updated due to errors." go away on 64-bit systems. This makes no sense to me as cmake is already distributed with OpenFOAM. My source says that it helped him, but that OpenFOAM remains using the cmake-version delivered together with OpenFOAM-thirdparty, so it should pose no harm to do this.

/Mads

[suitup]

HA!

It worked, Mads! After installing cmake, startet allwmake in the applicationsfolder, it compiled the rest without problems, now i can read the openfoam-cases.

1000 thanks, I still dont believe it

[suitup]

Ok, don't halloo till you're out of the wood!

ParaView can now load the files without any crashes, but is not able to display the case and cannot read the timu-files, it stucks at time 0s.
Like written before with foamToVTK and loading the vtk-filecase into ParaView, ParaView is able to load the case and the timing-files and can display everything. I ve no clue.

OpenFoam-File



VTK-File




Should I switch to Ubuntu 32bit and OpenFoam 32bit? Wont there be any issues?

[akidess]

Originally Posted by MadsR

This just in :-) I've heard that running

apt-get install cmake

may help the "make: The target "application" was not updated due to errors." go away on 64-bit systems. This makes no sense to me as cmake is already distributed with OpenFOAM. My source says that it helped him, but that OpenFOAM remains using the cmake-version delivered together with OpenFOAM-thirdparty, so it should pose no harm to do this.

/Mads

A possible explanation is that at that point of the setup the $PATH variable is not yet set to the OpenFOAM thirdparty stuff (or at least not to cmake), so it is not found by the system. If encountering that error, either installing cmake, or manually changing $PATH to include the cmake that comes with OpenFOAM.

[elvisjohndowson]

Hi,
I just downloaded OpenFOAM-1.6 and ThirdParty-1.6 sources, and applied the v2 patches. I am trying to compile OpenFOAM on Mac OS X 1.6.1, using the default gcc compiler. What I did was modify the OpenFOAM patch and change all the entries for gcc-mp-4.3 to gcc, g++-mp-4.3 to g++ and cpp-mp-4.3 to cpp, since those compiler versions are not part of the standard distribution for 10.6.1.

When I try to run ./Allwmake, I get the following errors:

Making dependency list for source file hoard-371/src/libhoard.cpp
SOURCE=hoard-371/src/libhoard.cpp ; g++ -m64 -DdarwinIntel64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -DNDEBUG -D_REENTRANT=1 -IlnInclude -I. -I/Users/elvis/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/Users/elvis/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude -fPIC -Ddarwin -c $SOURCE -o Make/darwinIntel64DPOpt/libhoard.o
In file included from /usr/include/c++/4.2.1/bits/char_traits.h:45,
from /usr/include/c++/4.2.1/string:47,
from /Users/elvis/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude/string.h:52,
from lnInclude/ansiwrapper.h:7,
from hoard-371/src/libhoard.cpp:92:
/usr/include/c++/4.2.1/cstring:80: error: ‘::memcpy’ has not been declared
/usr/include/c++/4.2.1/cstring:81: error: ‘::memmove’ has not been declared
/usr/include/c++/4.2.1/cstring:82: error: ‘::strcpy’ has not been declared
/usr/include/c++/4.2.1/cstring:83: error: ‘::strncpy’ has not been declared


Best regards,

Elvis

[akidess]

Elvis, I don't see how your post is related to the cookbook. You might be better off reading threads / the wiki for hints on a MacOS installation or creating a new thread.

[MadsR]

@Akidess:

Quite possible indeed, nice. So maybe I should put an

echo "export PATH=$PATH:~/OpenFOAM/ThirdParty-1.6.x/cmake-2.6.4/platforms/linux/bin/ " >> ~/.bashrc

into the script?

/Mads

[dandiwijaya]

Hi all
I was just installing openFoam and try installing using the your script .The installation successful, but when I try blockmesh at cases cavity at tutorials there is perform the following message appears:

--> FOAM FATAL ERROR:
Failed writing polyMesh.

From function blockMesh
in file blockMeshApp.C at line 346.

one more thing, when I try to check the installation after trying the case had the following message appears:

Third party software
-------------------------------------------------------------------------------
Software Version Location
-------------------------------------------------------------------------------
gcc 4.3.3
WARNING: Conflicting installations:
OpenFOAM settings : /home/dandiwijaya/OpenFOAM/ThirdParty-1.6.x/gcc-4.3.3/platforms/linux/bin/gcc
current path : /usr/bin/gcc
CRITICAL ERROR

gzip 1.3.12 /bin/gzip
tar 1.20 /bin/tar
Aborted
icoFoam 1.6.x .../OpenFOAM-1.6.x/applications/bin/linuxGccDPOpt/icoFoam
-------------------------------------------------------------------------------


Summary
-------------------------------------------------------------------------------
Base configuration ok.

The foam installation contains 1 critical error(s).

Review the output for warning messages and consult
the installation guide for trouble shooting.

done.

please help me guys, I'm still newbie in using openFoam

thanks

[suitup]

Ok to update you.

I tried installing OF 64bit with openSuse and i works.

Best regards.

Now I just have to get salome working.

[akidess]

Originally Posted by MadsR

@Akidess:

Quite possible indeed, nice. So maybe I should put an

echo "export PATH=$PATH:~/OpenFOAM/ThirdParty-1.6.x/cmake-2.6.4/platforms/linux/bin/ " >> ~/.bashrc

into the script?

/Mads

First off, you can call me Anton.

I don't think adding the path permanently to bashrc is the best solution. I think it would be better to either add cmake to apt-get (cmake probably doesn't change so much a different version will break it), or just export the path to the OpenFOAM cmake temporarily for the script, as it should be there once the OpenFOAM .bashrc is sourced: "export PATH=$PATH:~/OpenFOAM/ThirdParty-1.6.x/cmake-2.6.4/platforms/linux/bin/ "

Also, did you remember to include "set -e" into the script?

[MadsR]

Okay...64 bit Ubuntu should also work with the script, according to above posts. I think that Ubuntu is way easier to use (having used Linux since mid '90) but that's probably a matter of taste more than anything else.

Main thing: you got OF running :-) happy foaming!

/Mads

[MadsR]

Hi Anton!

Actually I already did add cmake to the apt-get as an easy solution, so I'll just stick to that, as you suggest. Yes, set -e has been included :-)

Cheers!
Mads

[JinBiao]

Hi Mads and Akidess. Thanks a lot for the help. Yes, I did update the libs during the compile-error-recompile process. It can be reason. And the error I got when I compile the applications has been settled by apt-get install cmake.

Jin

Originally Posted by MadsR

It's odd, it should work on a non-altered Ubuntu. If you are updating stuff (libs) in the middle of a compile-error-recompile loop, you might get into trouble. Maybe you want to remove OpenFOAM-1.6.x completely and redo the git-part and then the ./Allwmake once more to be sure that linking is done correctly ? This might also be a complete waste of time :-/ but if you do not have anything else to try, it might be worth it.

/Mads

[skinduptruk]

thanks for the cookbook

i have a few questions mostly related to linux knowledge (lack thereof)

the wiki has a different git address, this one worked for me, the cookbook one didn't (something about socket error). note the path with 'r'

git clone http://repo.or.cz/r/OpenFOAM-1.6.x.git/

i then needed to do a git merge origin/master command that the cookbook didn't have. this gave me the dirs rather than the .git alone. is this to do with using a different git address as above? is what i've done going to work?

also the wiki has a compiler change from OpenFOAM to System - is this still needed? i did this just in case.

finally the wiki says to compile the 3rd party stuff, but i note the OF makefile does this already

anyway, i'm now at the end of the cookbook and have run the wmake and it seems to be ok so far using tail make.log, i know it takes hours.

thanks again, i wouldn't have built from source without this cookbook.

[MadsR]

Hi Kurt.

I am glad the script worked out. I do not understand your git issue and why the r-directory should be added to the url :-) ?

With regards to the wiki I can't help, I guess everything should work when the script runs to the end without errors, no?

/Mads