GroovyBC the dynamic cousin of funkySetFields that lives on the suburb of the mesh

philippose · February 18, 2010, 12:55

Hello again :-)!

So... here are some screenshots of the case I have been referring to.... They are images taken after about 400 iterations (a normal run for this case would go up to around 1500 or so), so the fields may not have converged completely.

The yellow coloured patch is the inlet patch, and the green coloured one is the outletLS patch. The outlet patch is the third face which I did not colour specifically.

The case is basically a hydraulic spool, in which the pressure at the outlet is held constant at around 20 bar or so, and a constant flow of around 0.8 l/min flows out of the outletLS patch.

groovyBC couples the inlet patch to outletLS with the condition that the uniform pressure at the inlet be always 9.5 bar higher than the average pressure at outletLS.

As I mentioned in my previous post, groovyBC handles this scenario quite well :-)!

Have a nice day ahead!

Philippose

gschaider · February 18, 2010, 15:16

Quote:

Originally Posted by philippose

I thought I would give you a first status update regarding the coupling facility you added to groovyBC recently:

1. I checked out the OF-1.6 version of groovyBC from SVN today, and directly, without making any changes, compiled it on OpenFOAM-1.5-dev.... Result: It worked without a hitch :-) So it looks like you could simply copy all the changes you made on the 1.6-branch of groovyBC to the 1.5-branch

Great. But also 2 demo-cases have to be adapted and the new one backported. So I'll do it when I find the time. But if somebody beats me to it, that's alright, too

Bernhard

philippose · February 20, 2010, 05:10

Hello Bernhard,

A Good Morning to you! Hope the weekend started off well....!

I was looking into the Demo files of the two versions of groovyBC (OF-1.5 and OF-1.6) to see what really needs to be modified, and found the following:

[*** Note: As mentioned earlier, I was able to compile the latest version of groovyBC located in the "Breeder-1.6" SVN folder on OpenFOAM-1.5-dev without having to make any modifications ****]

1. Of course, the case average-t-junction does not exist in the OF-1.5 version.... I have finished back-porting this case, and it now works fine on OpenFOAM-1.5-dev with the new version of groovyBC

2. I had to modify the "U" field of the pulsedPitzDaily case in order to make it compatible with the new version of groovyBC, and it runs fine now on OpenFOAM-1.5-dev

3. I had to make no changes to the wobbler case, and it ran "out-of-the-box" with the new version of groovyBC on OpenFOAM-1.5-dev

4. No modifications to the movingConeDistorted case was required, and it too ran with the new version of groovyBC on OpenFOAM-1.5-dev

5. I am not completely sure of the circulatingSplash case, because I dont have PyFoam installed, but on looking into the case, I think the only modification required would be in the "gamma" field.... where the toFace in the "r1" variable will have to be removed...... I ran the case on OpenFOAM-1.5-dev using "interFoam" after making this change to the "gamma" field, but got the error:

Code:

Create mesh for time = 0


Reading environmentalProperties
Reading field pd

Reading field gamma

Reading field U

Reading/calculating face flux field phi

Reading transportProperties

Selecting incompressible transport model Newtonian
Selecting incompressible transport model Newtonian
Calculating field g.h

time step continuity errors : sum local = 0, global = 0, cumulative = 0
PCG:  Solving for pcorr, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0, global = 0, cumulative = 0
Courant Number mean: 0 max: 0 velocity magnitude: 0

Starting time loop

Courant Number mean: 0 max: 0 velocity magnitude: 0
deltaT = 0.00025
Time = 0.00025

MULES: Solving for gamma
Liquid phase volume fraction = 0  Min(gamma) = 0  Max(gamma) = 1
MULES: Solving for gamma
Liquid phase volume fraction = 0  Min(gamma) = 0  Max(gamma) = 1
MULES: Solving for gamma
Liquid phase volume fraction = 0  Min(gamma) = 0  Max(gamma) = 1
GAMG:  Solving for pd, Initial residual = 1, Final residual = 0.02034469, No Iterations 3
GAMG:  Solving for pd, Initial residual = 0.7797756, Final residual = 0.01510108, No Iterations 3


keyword agglomerator is undefined in dictionary ""

file:  from line 0 to line 0.

    From function dictionary::lookupEntry(const word& keyword) const
    in file db/dictionary/dictionary.C at line 213.

FOAM exiting

I dont think this is directly connected with groovyBC, but it is unusual, that I do not get any information as to which solver and field is being referred to in the error.... I looked into "fvSolution", and all the solvers which use "GAMG" as the main solver or as the pre-conditioner have the "agglomerator" keyword as usual... couldn't locate the error...... any ideas??

So basically as far as groovyBC is concerned, I think we have everything required and ready, to back-port the changes in the OF-1.6 version of groovyBC to the OF-1.5 version.....

What would be the best way to implement the changes? Shall I send you a zipped copy of the entire folder.... so that you could quickly check if everything is ok and update the SVN?

Have a nice weekend ahead!

Philippose

ngj · February 20, 2010, 13:44

Hi Philippose

I had a similar error, however requesting "smoother" undefined otherwise identical error message.
I believe I tracked it down to either pcorr or pdFinal in fvSolution, however I was unable to resolve the problem. The solution was to change the solver to basic PCG, however it would be nice to resolve the error instead.

A good weekend to you as well.

Best regards,

Niels

bastil · February 22, 2010, 06:15

I have problems building groovyBC (and also funkySetFields) on our system against both 1.6(.x) and 1.5.x/1.5-dev. For the vanilla 1.6 I get:

Code:

ValueExpressionLexer.ll:136: error: ‘class ValueExpressionDriver’ has no member named ‘isVector’

I have already done an update to bison 2.4.1 without sucess. Any suggestions? I use the latest svn.

Regards BastiL

gschaider · February 24, 2010, 08:17

Quote:

Originally Posted by bastil

I have problems building groovyBC (and also funkySetFields) on our system against both 1.6(.x) and 1.5.x/1.5-dev. For the vanilla 1.6 I get:

Code:

ValueExpressionLexer.ll:136: error: ‘class ValueExpressionDriver’ has no member named ‘isVector’

I have already done an update to bison 2.4.1 without sucess. Any suggestions? I use the latest svn.

Regards BastiL

Are you using this one (use "svn info" to check)? https://openfoam-extend.svn.sourcefo...funkySetFields Because the isVector-stuff is present only in veeeery old versions. Use "svn status -v ValueExpressionLexer.ll" to check whether that file is at version 1608 (second number) Bernhard

gschaider · February 24, 2010, 08:28

Quote:

Originally Posted by philippose

Hello Bernhard,

A Good Morning to you! Hope the weekend started off well....!

I was looking into the Demo files of the two versions of groovyBC (OF-1.5 and OF-1.6) to see what really needs to be modified, and found the following:

[*** Note: As mentioned earlier, I was able to compile the latest version of groovyBC located in the "Breeder-1.6" SVN folder on OpenFOAM-1.5-dev without having to make any modifications ****]

1. Of course, the case average-t-junction does not exist in the OF-1.5 version.... I have finished back-porting this case, and it now works fine on OpenFOAM-1.5-dev with the new version of groovyBC

.... snipped ..... What would be the best way to implement the changes? Shall I send you a zipped copy of the entire folder.... so that you could quickly check if everything is ok and update the SVN?

Have a nice weekend ahead!

Philippose

Hi Philipose! Thanks for looking through these things. To be honest: I'd prefer it if someone who is interested (you?) took over the maintainance of that old branch. If you feel like doing that I can set you up for svn write access. Otherwise mail me the tar Bernhard

bastil · February 25, 2010, 02:57

Quote:

Originally Posted by gschaider

Are you using this one (use "svn info" to check)?

Bernhard, thanks for your help. I started with funkySetFields skipping groovyBC at the moments:

Code:

svn status -v ValueExpressionLexer.ll
              1669     1608 bgschaid     ValueExpressionLexer.ll
 svn info
Path: .
URL: https://openfoam-extend.svn.sourceforge.net/svnroot/openfoam-extend/trunk/Breeder_1.6/utilities/postProcessing/FunkySetFields/funkySetFields
Repository Root: https://openfoam-extend.svn.sourceforge.net/svnroot/openfoam-extend
Repository UUID: e4e07f05-0c2f-0410-a05a-b8ba57e0c909
Revision: 1669
Node Kind: directory
Schedule: normal
Last Changed Author: bgschaid
Last Changed Rev: 1611
Last Changed Date: 2010-01-26 11:24:56 +0100 (Tue, 26 Jan 2010)

Code:

wmake libso
wmakeLnInclude: linking include files to ./lnInclude
Making dependency list for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy

I am not really sure that is going wrong. This was my build against the native vanillia 1.6...

Regards Basti

gschaider · February 25, 2010, 08:48

Quote:

Originally Posted by bastil

Bernhard, thanks for your help. I started with funkySetFields skipping groovyBC at the moments:

Code:

svn status -v ValueExpressionLexer.ll
              1669     1608 bgschaid     ValueExpressionLexer.ll
 svn info
Path: .
URL: https://openfoam-extend.svn.sourceforge.net/svnroot/openfoam-extend/trunk/Breeder_1.6/utilities/postProcessing/FunkySetFields/funkySetFields
Repository Root: https://openfoam-extend.svn.sourceforge.net/svnroot/openfoam-extend
Repository UUID: e4e07f05-0c2f-0410-a05a-b8ba57e0c909
Revision: 1669
Node Kind: directory
Schedule: normal
Last Changed Author: bgschaid
Last Changed Rev: 1611
Last Changed Date: 2010-01-26 11:24:56 +0100 (Tue, 26 Jan 2010)

Looks Fine

Quote:

Originally Posted by bastil

Code:

wmake libso
wmakeLnInclude: linking include files to ./lnInclude
Making dependency list for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy

I am not really sure that is going wrong. This was my build against the native vanillia 1.6...

Those missing files are alright. They are create from the Lexer.ll and therefor CAN'T be there. Does the rest of the compilation work?
Bernhard

bastil · February 25, 2010, 12:45

Quote:

Originally Posted by gschaider

Does the rest of the compilation work?
Bernhard

Of course not....

Code:

wmake
Making dependency list for source file ValueExpressionLexer.C
Making dependency list for source file ValueExpressionParser.C
Making dependency list for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
SOURCE=ValueExpressionLexer.C ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionLexer.o
SOURCE=ValueExpressionParser.C ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionParser.o
lex.ve.c:340: warning: use of old-style cast
lex.ve.c:410: warning: use of old-style cast
lex.ve.c:410: warning: use of old-style cast
In file included from ValueExpressionParser.yy:62,
                 from ValueExpressionParser.tab.cc:68:
ValueExpressionDriver.H:23: error: incomplete type ‘ve::ValueExpressionParser’ used in nested name specifier
ValueExpressionDriver.H:23: error: ‘yylval’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘*’ token
ValueExpressionDriver.H:23: error: ‘yylloc’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘&’ token
ValueExpressionDriver.H:23: error: ‘driver’ was not declared in this scope
ValueExpressionDriver.H:23: error: initializer expression list treated as compound expression
ValueExpressionParser.tab.cc:158: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:192: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:202: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:213: error: expected ‘,’ or ‘...’ before ‘*’ token
ValueExpressionParser.tab.cc:213: error: ISO C++ forbids declaration of ‘semantic_type’ with no type
ValueExpressionParser.tab.cc:213: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:362: error: expected ‘,’ or ‘...’ before ‘*’ token
ValueExpressionParser.tab.cc:362: error: ISO C++ forbids declaration of ‘semantic_type’ with no type
ValueExpressionParser.tab.cc:362: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:374: error: ‘semantic_type’ has not been declared
ValueExpressionParser.tab.cc:374: error: ‘location_type’ has not been declared
ValueExpressionParser.tab.cc:374: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:508: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:517: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:523: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:529: error: ‘debug_level_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:536: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:536: error: ‘debug_level_type’ was not declared in this scope
ValueExpressionParser.tab.cc:543: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2119: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2169: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2171: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2240: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2307: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2315: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2324: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2326: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2561: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2797: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2866: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2884: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2909: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2936: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2967: error: ‘rhs_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:3056: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3081: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3106: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3117: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3134: error: ‘token_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:3183: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3184: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3185: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3186: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3187: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3188: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3189: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3190: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3192: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3193: error: ‘token_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.yy:380: error: expected unqualified-id before ‘&’ token
ValueExpressionParser.yy:380: error: expected ‘,’ or ‘...’ before ‘&’ token
ValueExpressionParser.yy:380: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
make: *** [Make/linux64GccDPOpt/ValueExpressionParser.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from ValueExpressionParser.yy:63,
                 from ValueExpressionDriver.H:14,
                 from ValueExpressionLexer.ll:3:
ValueExpressionDriverLogicalTemplates.H:7: error: expected initializer before ‘<’ token
ValueExpressionDriverLogicalTemplates.H:13: error: expected initializer before ‘<’ token
ValueExpressionDriverLogicalTemplates.H:48: error: invalid use of incomplete type ‘struct ValueExpressionDriver’
ValueExpressionDriver.H:12: error: forward declaration of ‘struct ValueExpressionDriver’
ValueExpressionDriverLogicalTemplates.H:74: error: invalid use of incomplete type ‘struct ValueExpressionDriver’
ValueExpressionDriver.H:12: error: forward declaration of ‘struct ValueExpressionDriver’
ValueExpressionDriverLogicalTemplates.H:105: error: invalid use of incomplete type ‘struct ValueExpressionDriver’
ValueExpressionDriver.H:12: error: forward declaration of ‘struct ValueExpressionDriver’
ValueExpressionDriverLogicalTemplates.H:133: error: invalid use of incomplete type ‘struct ValueExpressionDriver’
ValueExpressionDriver.H:12: error: forward declaration of ‘struct ValueExpressionDriver’
In file included from ValueExpressionLexer.ll:3:
ValueExpressionDriver.H:23: error: incomplete type ‘ve::ValueExpressionParser’ used in nested name specifier
ValueExpressionDriver.H:23: error: ‘yylval’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘*’ token
ValueExpressionDriver.H:23: error: ‘yylloc’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘&’ token
ValueExpressionDriver.H:23: error: ‘driver’ was not declared in this scope
ValueExpressionDriver.H:23: error: initializer expression list treated as compound expression
lex.ve.c:8769: error: redefinition of ‘int velex’
ValueExpressionDriver.H:23: error: ‘int velex’ previously defined here
lex.ve.c:8769: error: incomplete type ‘ve::ValueExpressionParser’ used in nested name specifier
lex.ve.c:8769: error: ‘yylval’ was not declared in this scope
lex.ve.c:8769: error: expected primary-expression before ‘*’ token
lex.ve.c:8769: error: ‘yylloc’ was not declared in this scope
lex.ve.c:8769: error: expected primary-expression before ‘&’ token
lex.ve.c:8769: error: ‘driver’ was not declared in this scope
lex.ve.c:306: warning: ‘yy_buffer_stack_top’ defined but not used
lex.ve.c:307: warning: ‘yy_buffer_stack_max’ defined but not used
lex.ve.c:308: warning: ‘yy_buffer_stack’ defined but not used
lex.ve.c:335: warning: ‘yy_hold_char’ defined but not used
lex.ve.c:336: warning: ‘yy_n_chars’ defined but not used
lex.ve.c:340: warning: ‘yy_c_buf_p’ defined but not used
lex.ve.c:341: warning: ‘yy_init’ defined but not used
lex.ve.c:342: warning: ‘yy_start’ defined but not used
lex.ve.c:347: warning: ‘yy_did_buffer_switch_on_eof’ defined but not used
lex.ve.c:360: warning: ‘void veensure_buffer_stack()’ declared ‘static’ but never defined
lex.ve.c:361: warning: ‘void ve_load_buffer_state()’ declared ‘static’ but never defined
lex.ve.c:362: warning: ‘void ve_init_buffer(yy_buffer_state*, FILE*)’ declared ‘static’ but never defined
lex.ve.c:8401: warning: ‘yy_state_type yy_get_previous_state()’ declared ‘static’ but never defined
lex.ve.c:8402: warning: ‘yy_state_type yy_try_NUL_trans(yy_state_type)’ declared ‘static’ but never defined
lex.ve.c:8403: warning: ‘int yy_get_next_buffer()’ declared ‘static’ but never defined
lex.ve.c:8404: warning: ‘void yy_fatal_error(const char*)’ declared ‘static’ but never defined
lex.ve.c:8484: warning: ‘yy_last_accepting_state’ defined but not used
lex.ve.c:8485: warning: ‘yy_last_accepting_cpos’ defined but not used
lex.ve.c:8596: warning: ‘int yy_init_globals()’ declared ‘static’ but never defined
lex.ve.c:8636: warning: ‘int yyinput()’ declared ‘static’ but never defined
lex.ve.c:8647: warning: ‘yy_start_stack_ptr’ defined but not used
lex.ve.c:8648: warning: ‘yy_start_stack_depth’ defined but not used
lex.ve.c:8649: warning: ‘yy_start_stack’ defined but not used
lex.ve.c:8651: warning: ‘void yy_push_state(int)’ declared ‘static’ but never defined
lex.ve.c:8653: warning: ‘void yy_pop_state()’ declared ‘static’ but never defined
lex.ve.c:8655: warning: ‘int yy_top_state()’ declared ‘static’ but never defined
make: *** [Make/linux64GccDPOpt/ValueExpressionLexer.o] Error 1

gschaider · February 26, 2010, 09:33

Quote:

Originally Posted by bastil

Of course not....

Code:

wmake
Making dependency list for source file ValueExpressionLexer.C
Making dependency list for source file ValueExpressionParser.C
Making dependency list for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
SOURCE=ValueExpressionLexer.C ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionLexer.o
SOURCE=ValueExpressionParser.C ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionParser.o
lex.ve.c:340: warning: use of old-style cast
lex.ve.c:410: warning: use of old-style cast
lex.ve.c:410: warning: use of old-style cast
In file included from ValueExpressionParser.yy:62,
make: *** [Make/linux64GccDPOpt/ValueExpressionLexer.o] Error 1

Noticed that the output of two compilation commands is mixed in your output. Have you got the environment variable WM_NCOMPPROCS set to something higher than 1. Don't know if that is the cause but you could be the victim of a very ugly race-condition (the outputs of the yy and ll-files depend on each other)
Other thing: the compilation you do here: did you use the insertGenerated-script by any chance? Because I'm not 100% sure if the generated files in the SVN are up-to-date
Bernhard

bastil · February 26, 2010, 09:48

Quote:

Originally Posted by gschaider

Noticed that the output of two compilation commands is mixed in your output. Have you got the environment variable WM_NCOMPPROCS set to something higher than 1.

Yes it defaults to 2. I changed it to 1. Error stays the same...

Quote:

Other thing: the compilation you do here: did you use the insertGenerated-script by any chance? Because I'm not 100% sure if the generated files in the SVN are up-to-date

You mean I have to use insertGenerated.sh before running wmake? I jhae not done this before but ran wclean and tried it and the error still remains the same...
If svn is not up-to-date, what is it? I have problems with all funkySetFields ad groovyBC with 1.5 and 1.6 OF-Line.

Regards Basti

philippose · February 26, 2010, 14:06

Quote:

Originally Posted by gschaider

Hi Philipose! Thanks for looking through these things. To be honest: I'd prefer it if someone who is interested (you?) took over the maintainance of that old branch. If you feel like doing that I can set you up for svn write access. Otherwise mail me the tar Bernhard

Hello again Bernhard,

Thanks for the reply.... :-)!

I think it should be possible for me to handle the 1.5 branch of groovyBC.... on the other hand, if you think its better to limit the number of people who have write access to the SVN, then I can send you the TAR package too :-)!

Have a nice evening!

Philippose

gschaider · March 1, 2010, 07:10

Quote:

Originally Posted by bastil

Yes it defaults to 2. I changed it to 1. Error stays the same...

OK.

Quote:

Originally Posted by bastil

You mean I have to use insertGenerated.sh before running wmake? I jhae not done this before but ran wclean and tried it and the error still remains the same...
If svn is not up-to-date, what is it? I have problems with all funkySetFields ad groovyBC with 1.5 and 1.6 OF-Line.

The reason why I was asking is, that your last error message started with

Code:

 SOURCE=ValueExpressionLexer.C; g++ ....

while in the regular case (without insertGenerated.sh) it starts with

Code:

 SOURCE=ValueExpressionLexer.ll ; rm Make/linux64GccDPOpt/ValueExpressionLexer.C ; flex -f $SOURCE ; mv *.c Make/linux64GccDPOpt/ValueExpressionLexer.C ; g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/home/bgschaid/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/home/bgschaid/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/home/bgschaid/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/home/bgschaid/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c Make/linux64GccDPOpt/ValueExpressionLexer.C -o Make/linux64GccDPOpt/ValueExpressionLexer.o

Anyway. Could you check the relevant versions with "bison -V", "flex -V" and "g++ -v"?. I also changed a more up-to-date version of the generated files to the svn of funky-1.6

gschaider · March 1, 2010, 07:16

Quote:

Originally Posted by philippose

Hello again Bernhard,

Thanks for the reply.... :-)!

I think it should be possible for me to handle the 1.5 branch of groovyBC.... on the other hand, if you think its better to limit the number of people who have write access to the SVN, then I can send you the TAR package too :-)!

The ideal solution would be: you promise to behave, tell me your Sourceforge-account-name and I'll set you up for write access. Write access is not meant to be an ultra-exclusive club (the more the merrier), it's just that we want to be sure that people know what they're doing (which I assume, you do)
Bernhard

bastil · March 1, 2010, 09:53

Quote:

Originally Posted by gschaider

Anyway. Could you check the relevant versions with "bison -V", "flex -V" and "g++ -v"?. I also changed a more up-to-date version of the generated files to the svn of funky-1.6

Bison: 2.41, flex 2.5.31, gcc 4.3.3 (from OpenFOAM)

I did a "svn update":

Code:

svn update
U    GeneratedFiles/ValueExpressionParser.C
U    GeneratedFiles/ValueExpressionLexer.C
U    ValueExpressionParser.output
Updated to revision 1670.

Code:

wmake
Making dependency list for source file ValueExpressionParser.C
Making dependency list for source file ValueExpressionLexer.C
Making dependency list for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
SOURCE=ValueExpressionParser.C ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionParser.o
In file included from ValueExpressionParser.yy:62,
                 from ValueExpressionParser.tab.cc:68:
ValueExpressionDriver.H:23: error: incomplete type ‘ve::ValueExpressionParser’ used in nested name specifier
ValueExpressionDriver.H:23: error: ‘yylval’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘*’ token
ValueExpressionDriver.H:23: error: ‘yylloc’ was not declared in this scope
ValueExpressionDriver.H:23: error: expected primary-expression before ‘&’ token
ValueExpressionDriver.H:23: error: ‘driver’ was not declared in this scope
ValueExpressionDriver.H:23: error: initializer expression list treated as compound expression
ValueExpressionParser.tab.cc:158: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:192: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:202: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:213: error: expected ‘,’ or ‘...’ before ‘*’ token
ValueExpressionParser.tab.cc:213: error: ISO C++ forbids declaration of ‘semantic_type’ with no type
ValueExpressionParser.tab.cc:213: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:362: error: expected ‘,’ or ‘...’ before ‘*’ token
ValueExpressionParser.tab.cc:362: error: ISO C++ forbids declaration of ‘semantic_type’ with no type
ValueExpressionParser.tab.cc:362: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:374: error: ‘semantic_type’ has not been declared
ValueExpressionParser.tab.cc:374: error: ‘location_type’ has not been declared
ValueExpressionParser.tab.cc:374: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:508: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:517: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:523: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:529: error: ‘debug_level_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:536: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:536: error: ‘debug_level_type’ was not declared in this scope
ValueExpressionParser.tab.cc:543: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2119: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2169: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2171: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2240: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2307: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2315: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2324: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2326: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2561: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2797: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2866: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2884: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2909: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2936: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:2967: error: ‘rhs_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:3056: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3081: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3106: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3117: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3134: error: ‘token_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.tab.cc:3183: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3184: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3185: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3186: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3187: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3188: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3189: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3190: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3192: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
ValueExpressionParser.tab.cc:3193: error: ‘token_number_type’ in class ‘ve::ValueExpressionParser’ does not name a type
ValueExpressionParser.yy:380: error: expected unqualified-id before ‘&’ token
ValueExpressionParser.yy:380: error: expected ‘,’ or ‘...’ before ‘&’ token
ValueExpressionParser.yy:380: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
make: *** [Make/linux64GccDPOpt/ValueExpressionParser.o] Error 1

gschaider · March 2, 2010, 12:49

Quote:

Originally Posted by bastil

Bison: 2.41, flex 2.5.31, gcc 4.3.3 (from OpenFOAM)

These look fine (I use the same except for the compiler which differs slightly)

Quote:

Originally Posted by bastil

I did a "svn update":

Code:

wmake
Making dependency list for source file ValueExpressionParser.C
Making dependency list for source file ValueExpressionLexer.C
Making dependency list for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C

If it starts like this then you're working on sources where you used insertGenerated.sh, because in the regular case it should start like this:

Code:

 Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy
  Making dependency list for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionDriver.C
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionDriver.C

Either try a completly fresh svn checkout or do "svn revert Make/files", then a wclean and a wmake

Bernhard

bastil · March 3, 2010, 07:32

Quote:

Originally Posted by gschaider

Either try a completly fresh svn checkout or do "svn revert Make/files", then a wclean and a wmake

I did a fresh checkout:

Code:

wmake
Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy
Making dependency list for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionDriver.C
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
could not open file ValueExpressionParser.tab.hh for source file funkySetFields.C
SOURCE=ValueExpressionParser.yy ; rm -f Make/linux64GccDPOpt/ValueExpressionParser.C Make/linux64GccDPOpt/ValueExpressionParser.tab.hh; bison -ra -v  -d $SOURCE ;  mv *.tab.cc Make/linux64GccDPOpt/ValueExpressionParser.C ; mv *.tab.hh Make/linux64GccDPOpt/ValueExpressionParser.tab.hh ; mv *.hh Make/linux64GccDPOpt ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c  Make/linux64GccDPOpt/ValueExpressionParser.C -o Make/linux64GccDPOpt/ValueExpressionParser.o
/opt/bison/2.4.1/share/bison/location.cc:24: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/location.cc:148: /usr/bin/m4: Warning: Excess arguments to built-in `m4_if' ignored
/opt/bison/2.4.1/share/bison/location.cc:148: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/location.cc:274: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/lalr1.cc:300: /usr/bin/m4: Warning: Excess arguments to built-in `m4_if' ignored
/opt/bison/2.4.1/share/bison/lalr1.cc:300: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
NONE:0: /usr/bin/m4: ERROR: EOF in string
bison: subsidiary program `/usr/bin/m4' failed (exit status 1)
mv: cannot stat `*.tab.cc': No such file or directory
mv: cannot stat `*.tab.hh': No such file or directory
g++: Make/linux64GccDPOpt/ValueExpressionParser.C: No such file or directory
g++: no input files
make: *** [Make/linux64GccDPOpt/ValueExpressionParser.o] Error 1

gschaider · March 3, 2010, 09:36

Quote:

Originally Posted by bastil

I did a fresh checkout:

Code:

wmake
Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy
Making dependency list for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionDriver.C
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
could not open file ValueExpressionParser.tab.hh for source file funkySetFields.C
SOURCE=ValueExpressionParser.yy ; rm -f Make/linux64GccDPOpt/ValueExpressionParser.C Make/linux64GccDPOpt/ValueExpressionParser.tab.hh; bison -ra -v  -d $SOURCE ;  mv *.tab.cc Make/linux64GccDPOpt/ValueExpressionParser.C ; mv *.tab.hh Make/linux64GccDPOpt/ValueExpressionParser.tab.hh ; mv *.hh Make/linux64GccDPOpt ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c  Make/linux64GccDPOpt/ValueExpressionParser.C -o Make/linux64GccDPOpt/ValueExpressionParser.o
/opt/bison/2.4.1/share/bison/location.cc:24: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/location.cc:148: /usr/bin/m4: Warning: Excess arguments to built-in `m4_if' ignored
/opt/bison/2.4.1/share/bison/location.cc:148: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/location.cc:274: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
/opt/bison/2.4.1/share/bison/lalr1.cc:300: /usr/bin/m4: Warning: Excess arguments to built-in `m4_if' ignored
/opt/bison/2.4.1/share/bison/lalr1.cc:300: /usr/bin/m4: Warning: Excess arguments to built-in `_m4_popdef' ignored
NONE:0: /usr/bin/m4: ERROR: EOF in string
bison: subsidiary program `/usr/bin/m4' failed (exit status 1)
mv: cannot stat `*.tab.cc': No such file or directory
mv: cannot stat `*.tab.hh': No such file or directory
g++: Make/linux64GccDPOpt/ValueExpressionParser.C: No such file or directory
g++: no input files
make: *** [Make/linux64GccDPOpt/ValueExpressionParser.o] Error 1

I wasn't aware that bison uses m4 (you learn something new every day). That program is really out of my league. But I don't think that it is a version issue. I'm afraid there is a very subtle problem with your system (some installation broken, permission, ...). I don't know much about m4. Make sure that it works on your machine (there is for instance an article about generating blockMeshes with m4 on the Wiki). Maybe someone with more knowledge about m4 could have an ide what is wrong
Bernhard

bastil · March 3, 2010, 11:14

Quote:

Originally Posted by gschaider

I wasn't aware that bison uses m4 (you learn something new every day). That program is really out of my league. But I don't think that it is a version issue. I'm afraid there is a very subtle problem with your system (some installation broken, permission, ...). I don't know much about m4. Make sure that it works on your machine (there is for instance an article about generating blockMeshes with m4 on the Wiki). Maybe someone with more knowledge about m4 could have an ide what is wrong
Bernhard

That seems to be an issue of the non-system bison 2.4.1 which does not work with the system m4. I tried the system bison 2.1 and now I get:

Code:

wmake
Making dependency list for source file ValueExpressionParser.yy
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionParser.yy
Making dependency list for source file ValueExpressionLexer.ll
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionLexer.ll
Making dependency list for source file ValueExpressionDriver.C
could not open file ValueExpressionParser.tab.hh for source file ValueExpressionDriver.C
Making dependency list for source file funkySetFields.C
could not open file ValueExpressionParser.tab.hh for source file funkySetFields.C
SOURCE=ValueExpressionParser.yy ; rm -f Make/linux64GccDPOpt/ValueExpressionParser.C Make/linux64GccDPOpt/ValueExpressionParser.tab.hh; bison -ra -v  -d $SOURCE ;  mv *.tab.cc Make/linux64GccDPOpt/ValueExpressionParser.C ; mv *.tab.hh Make/linux64GccDPOpt/ValueExpressionParser.tab.hh ; mv *.hh Make/linux64GccDPOpt ;  g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3  -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/opt/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/meshTools/lnInclude -IlnInclude -I. -I/opt/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/opt/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude   -fPIC -c  Make/linux64GccDPOpt/ValueExpressionParser.C -o Make/linux64GccDPOpt/ValueExpressionParser.o
In file included from ValueExpressionParser.yy:62,
                 from Make/linux64GccDPOpt/ValueExpressionParser.C:24:
./ValueExpressionDriver.H:23: error: incomplete type ‘ve::ValueExpressionParser’ used in nested name specifier
./ValueExpressionDriver.H:23: error: ‘yylval’ was not declared in this scope
./ValueExpressionDriver.H:23: error: expected primary-expression before ‘*’ token
./ValueExpressionDriver.H:23: error: ‘yylloc’ was not declared in this scope
./ValueExpressionDriver.H:23: error: expected primary-expression before ‘&’ token
./ValueExpressionDriver.H:23: error: ‘driver’ was not declared in this scope
./ValueExpressionDriver.H:23: error: initializer expression list treated as compound expression
ValueExpressionParser.tab.cc: In member function ‘virtual int yy::ValueExpressionParser::parse()’:
ValueExpressionParser.tab.cc:409: error: ‘velex’ cannot be used as a function
ValueExpressionParser.tab.cc: In member function ‘unsigned char yy::ValueExpressionParser::yytranslate_(int)’:
ValueExpressionParser.tab.cc:2633: warning: use of old-style cast
ValueExpressionParser.yy: At global scope:
ValueExpressionParser.yy:382: error: expected unqualified-id before ‘&’ token
ValueExpressionParser.yy:382: error: expected ‘,’ or ‘...’ before ‘&’ token
ValueExpressionParser.yy:382: error: invalid use of incomplete type ‘struct ve::ValueExpressionParser’
./ValueExpressionDriver.H:18: error: forward declaration of ‘struct ve::ValueExpressionParser’
make: *** [Make/linux64GccDPOpt/ValueExpressionParser.o] Error 1

February 22, 2010, 06:15	Building Problems	#85
bastil Senior Member BastiL Join Date: Mar 2009 Posts: 462 Rep Power: 9	I have problems building groovyBC (and also funkySetFields) on our system against both 1.6(.x) and 1.5.x/1.5-dev. For the vanilla 1.6 I get: Code: ValueExpressionLexer.ll:136: error: ‘class ValueExpressionDriver’ has no member named ‘isVector’ I have already done an update to bison 2.4.1 without sucess. Any suggestions? I use the latest svn. Regards BastiL

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Running funkySetFields	sara	OpenFOAM Running, Solving & CFD	10	October 3, 2012 10:08
FunkySetFields for OF 141	mer	OpenFOAM Pre-Processing	68	May 5, 2011 04:25
FunkySetFields dictionary	gschaider	OpenFOAM Running, Solving & CFD	14	December 3, 2008 21:13
FunkySetFields for cyclic bc	zakifoam	OpenFOAM Pre-Processing	1	December 18, 2007 07:24

February 20, 2010, 05:10		#83
philippose Senior Member Philippose Rajan Join Date: Mar 2009 Location: Germany Posts: 509 Rep Power: 13	Hello Bernhard, A Good Morning to you! Hope the weekend started off well....! I was looking into the Demo files of the two versions of groovyBC (OF-1.5 and OF-1.6) to see what really needs to be modified, and found the following: [ Note: As mentioned earlier, I was able to compile the latest version of groovyBC located in the "Breeder-1.6" SVN folder on OpenFOAM-1.5-dev without having to make any modifications *] 1. Of course, the case average-t-junction does not exist in the OF-1.5 version.... I have finished back-porting this case, and it now works fine on OpenFOAM-1.5-dev with the new version of groovyBC 2. I had to modify the "U" field of the pulsedPitzDaily case in order to make it compatible with the new version of groovyBC, and it runs fine now on OpenFOAM-1.5-dev 3. I had to make no changes to the wobbler case, and it ran "out-of-the-box" with the new version of groovyBC on OpenFOAM-1.5-dev 4. No modifications to the movingConeDistorted case was required, and it too ran with the new version of groovyBC on OpenFOAM-1.5-dev 5. I am not completely sure of the circulatingSplash case, because I dont have PyFoam installed, but on looking into the case, I think the only modification required would be in the "gamma" field.... where the toFace in the "r1" variable will have to be removed...... I ran the case on OpenFOAM-1.5-dev using "interFoam" after making this change to the "gamma" field, but got the error: Code: Create mesh for time = 0 Reading environmentalProperties Reading field pd Reading field gamma Reading field U Reading/calculating face flux field phi Reading transportProperties Selecting incompressible transport model Newtonian Selecting incompressible transport model Newtonian Calculating field g.h time step continuity errors : sum local = 0, global = 0, cumulative = 0 PCG: Solving for pcorr, Initial residual = 0, Final residual = 0, No Iterations 0 time step continuity errors : sum local = 0, global = 0, cumulative = 0 Courant Number mean: 0 max: 0 velocity magnitude: 0 Starting time loop Courant Number mean: 0 max: 0 velocity magnitude: 0 deltaT = 0.00025 Time = 0.00025 MULES: Solving for gamma Liquid phase volume fraction = 0 Min(gamma) = 0 Max(gamma) = 1 MULES: Solving for gamma Liquid phase volume fraction = 0 Min(gamma) = 0 Max(gamma) = 1 MULES: Solving for gamma Liquid phase volume fraction = 0 Min(gamma) = 0 Max(gamma) = 1 GAMG: Solving for pd, Initial residual = 1, Final residual = 0.02034469, No Iterations 3 GAMG: Solving for pd, Initial residual = 0.7797756, Final residual = 0.01510108, No Iterations 3 keyword agglomerator is undefined in dictionary "" file: from line 0 to line 0. From function dictionary::lookupEntry(const word& keyword) const in file db/dictionary/dictionary.C at line 213. FOAM exiting I dont think this is directly connected with groovyBC, but it is unusual, that I do not get any information as to which solver and field is being referred to in the error.... I looked into "fvSolution", and all the solvers which use "GAMG" as the main solver or as the pre-conditioner have the "agglomerator" keyword as usual... couldn't locate the error...... any ideas?? So basically as far as groovyBC is concerned, I think we have everything required and ready, to back-port the changes in the OF-1.6 version of groovyBC to the OF-1.5 version..... What would be the best way to implement the changes? Shall I send you a zipped copy of the entire folder.... so that you could quickly check if everything is ok and update the SVN? Have a nice weekend ahead! Philippose

February 20, 2010, 13:44		#84
ngj Senior Member Niels Gjoel Jacobsen Join Date: Mar 2009 Location: Rotterdam, The Netherlands Posts: 1,192 Rep Power: 19	Hi Philippose I had a similar error, however requesting "smoother" undefined otherwise identical error message. I believe I tracked it down to either pcorr or pdFinal in fvSolution, however I was unable to resolve the problem. The solution was to change the solver to basic PCG, however it would be nice to resolve the error instead. A good weekend to you as well. Best regards, Niels