[isa_]

Hi everybody! I'm a very basic user of linux and i'm experiencing big problems with funkySetFields installation.
I downloaded the tar.gz file and decompressed it into the preProcessing directory. I have versione 1.7 and open foam is installed in /opt directory. I tryed to do
,/Allwmake
to compile funkySetFields but i have this error: wmake not found

i tried to go back to the main openfoam directory and i did ./Allwmake there to compile the wmake command but i find this error

Error: Current directory in not $WM_PROJECT_DIR The environment variable are not consistent with the installation

i tried echo WM_PROJECT_DIR and i found out that actually i was in the project_dir.
can anyone help me please?
how can i compile the funkySetFields command?
i'm pretty sure the installation of the software is ok, also because i tried this on caelinux 2010 where openfoam is already installed.

[gschaider]

Originally Posted by isa_

Hi everybody! I'm a very basic user of linux and i'm experiencing big problems with funkySetFields installation.
I downloaded the tar.gz file and decompressed it into the preProcessing directory. I have versione 1.7 and open foam is installed in /opt directory. I tryed to do
,/Allwmake
to compile funkySetFields but i have this error: wmake not found

i tried to go back to the main openfoam directory and i did ./Allwmake there to compile the wmake command but i find this error

Error: Current directory in not $WM_PROJECT_DIR The environment variable are not consistent with the installation

i tried echo WM_PROJECT_DIR and i found out that actually i was in the project_dir.
can anyone help me please?
how can i compile the funkySetFields command?
i'm pretty sure the installation of the software is ok, also because i tried this on caelinux 2010 where openfoam is already installed.

This is not a FSF-problem, but a problem with your OF-setup. "wmake not found" means that a very essential part of your OF-installation is missing (the one that helps you compile OF-stuff - I doubt you have compiled anything else yet). Check again with "which wmake" if it finds nothing then there is a problem with your OF-installation.

./Allwmake in the OF-directory doesn't help

I guess that all your installations are from binary. Maybe there is a corresponding -dev package that brings wmake

Also check $WM_PROJECT_DIR/wmake for a file wmake (that is the one you're looking for). If it is there then probably $WM_PROJECT_DIR/wmake is not on your PATH (which it should be)

[isa_]

Thanks a lot for the answer.
I tried which make and it finds wmake in the $WM_PROJECT_DIR/wmake folder ($WM_PROJECT_DIR in my case is /opt/openfoam170).
so the command is there but when i compile funkysetfields it is not found.

i tried with ./Allwmake without sudo in the FunkySetFields directory and found
+ wmake funkySetFields
mkdir: cannot create directory `linux64GccDPOpt': Permission denied
/bin/sh: linux64GccDPOpt/options: No such file or directory
make: *** [linux64GccDPOpt/options] Error 1
/opt/openfoam170/wmake/MakefileFiles:39: linux64GccDPOpt/options: No such file or directory
make: *** No rule to make target `linux64GccDPOpt/options'. Stop.
wmake error: file 'Make/linux64GccDPOpt/objectFiles' could not be created


if i put sudo before, I get:
+ wmake funkySetFields
./Allwmake: line 4: wmake: command not found


i have never compiled anything before with open foam so i never used wmake.
i guess the wmake comand is not in my path as you said.
how can i check it and change it in case?
i'm a very very basic user and i'm getting a little bit desperate.
thanks

[gschaider]

Originally Posted by isa_

Thanks a lot for the answer.
I tried which make and it finds wmake in the $WM_PROJECT_DIR/wmake folder ($WM_PROJECT_DIR in my case is /opt/openfoam170).
so the command is there but when i compile funkysetfields it is not found.

i tried with ./Allwmake without sudo in the FunkySetFields directory and found
+ wmake funkySetFields
mkdir: cannot create directory `linux64GccDPOpt': Permission denied
/bin/sh: linux64GccDPOpt/options: No such file or directory
make: *** [linux64GccDPOpt/options] Error 1
/opt/openfoam170/wmake/MakefileFiles:39: linux64GccDPOpt/options: No such file or directory
make: *** No rule to make target `linux64GccDPOpt/options'. Stop.
wmake error: file 'Make/linux64GccDPOpt/objectFiles' could not be created


if i put sudo before, I get:
+ wmake funkySetFields
./Allwmake: line 4: wmake: command not found


i have never compiled anything before with open foam so i never used wmake.
i guess the wmake comand is not in my path as you said.
how can i check it and change it in case?
i'm a very very basic user and i'm getting a little bit desperate.
thanks

Your problems seem to be
a) you are not allowed to write the FSF-folder
b) root knows nothing about OpenFOAM

Solution: extract the FSF-sources AS YOURSELF (anywhere. They don't have to be in the OF-installation). Then wmake it. The binary goes to $FOAM_APPBIN (which is in your PATH)

[isa_]

Thanks a lot
it is almost working now but i still get an error:

everything goes fine till here where i get this error with ValueExpressionDriver.C and then everythings stops

from ValueExpressionDriver.C:3:
position.hh: In function ‘bool ve:perator==(const ve:osition&, const ve:osition&)’:
position.hh:136: warning: suggest parentheses around ‘&&’ within ‘||’
ValueExpressionDriver.C: In member function ‘Foam::surfaceScalarField* ValueExpressionDriver::makeAreaField()’:
ValueExpressionDriver.C:462: error: call of overloaded ‘GeometricField(Foam::IOobject, const Foam::fvMesh&, int)’ is ambiguous
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:420: note: candidates are: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dictionary&) [with Type = double, PatchField = Foam::fvsPatchField, GeoMesh = Foam::surfaceMesh]
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:256: note: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dimensioned<Type>&, const Foam::word&) [with Type = double, PatchField = Foam::fvsPatchField, GeoMesh = Foam::surfaceMesh]
ValueExpressionDriver.C: In member function ‘Foam::volScalarField* ValueExpressionDriver::makeVolumeField()’:
ValueExpressionDriver.C:482: error: call of overloaded ‘GeometricField(Foam::IOobject, const Foam::fvMesh&, int)’ is ambiguous
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:420: note: candidates are: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dictionary&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:256: note: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dimensioned<Type>&, const Foam::word&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
ValueExpressionDriver.C: In member function ‘Foam::volScalarField* ValueExpressionDriver::makeDistanceField()’:
ValueExpressionDriver.C:506: error: call of overloaded ‘GeometricField(Foam::IOobject, const Foam::fvMesh&, int)’ is ambiguous
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:420: note: candidates are: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dictionary&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:256: note: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dimensioned<Type>&, const Foam::word&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
ValueExpressionDriver.C: In member function ‘Foam::volScalarField* ValueExpressionDriver::makeRDistanceField(const Foam::volVectorField&)’:
ValueExpressionDriver.C:529: error: call of overloaded ‘GeometricField(Foam::IOobject, const Foam::fvMesh&, int)’ is ambiguous
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:420: note: candidates are: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dictionary&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
/opt/openfoam171/src/OpenFOAM/lnInclude/GeometricField.C:256: note: Foam::GeometricField<Type, PatchField, GeoMesh>::GeometricField(const Foam::IOobject&, const typename GeoMesh::Mesh&, const Foam::dimensioned<Type>&, const Foam::word&) [with Type = double, PatchField = Foam::fvPatchField, GeoMesh = Foam::volMesh]
make: *** [Make/linuxGccDPOpt/ValueExpressionDriver.o] Errore 1


i don't even understand if the last error is somehow connected with the previous ones.
any other hint?
thank you a lot

[gschaider]

Originally Posted by isa_

Thanks a lot
it is almost working now but i still get an error:

everything goes fine till here where i get this error with ValueExpressionDriver.C and then everythings stops

<snip>

i don't even understand if the last error is somehow connected with the previous ones.
any other hint?
thank you a lot

You said in the original posting "downloaded the tarball". One from http://openfoamwiki.net/index.php/Co...ncient_history ? There is a reason that this is called "ancient history". The 1.6-version downloaded via svn compiles on my 1.7.x version without problems

Bernhard

[isa_]

Thanks a lot
now it works fine. thanks for your patience.
but actually i didn't use the "ancient history" but i downloaded the .tar.gz from the link directly below the svn one in the Download section, probably that link is not updated.
thanks again

[gschaider]

Originally Posted by isa_

Thanks a lot
now it works fine. thanks for your patience.
but actually i didn't use the "ancient history" but i downloaded the .tar.gz from the link directly below the svn one in the Download section, probably that link is not updated.
thanks again

Seems like that link pointed to the 1.5 version. That is now fixed