Hrvoje Jasak

Help with invalid relocation type 42

What operating system are you on? Can you confirm as many of the variables as you can, eg. compiler, linker binutils etc? If I am reading this right, your bison isn't working either, meaning that there is something fundamentally broken with your installation. For the record, I am on Ubuntu-20.04 and 22.04 and stuff works. There were some problems with gcc-12, but it seems the compiler is broken.

New environment variables for locating the system-installed version of the Metis, ParMetis and Scotch packages.

Hi, The code fails in the thermo package because h boundary condition on the immersed boundary patch is set to a default patch field type (immersed boundary) that should not be used. There are options on how to fix this, ie either specify the h field or change the hBoundaryTypes to support immersed boundary. This is broken in the entire OpenFOAM, for all coupled implicit or special boundary types which are not spefically listed in functions such as hBoundaryTypes or heBoundaryTypes. A good virtual...

Problem with large parallel run: increasing memory usage with increasing number of nodes

Hi Guys, Sergey, thank you - excellent work. I have applied the patch on my machine: how can I test that everything is correct? Is it safe to push this into nextRelease and run with it fur a while? Hrv

This is bizarre. I am on gcc-9.3.0 and there isn't a problem. I think it will be because of unsigned ints. I don't want to change a compiler, and this is not related to c++-17 (I tried). What you can do is to take this constructor from label - there are 2: //- Construct from a list of labels // using the labels as indices to indicate which bits are set explicit inline PackedBoolList(const UList<label>& indices); //- Construct from a list of labels // using the labels as indices to indicate which...

Hi, You can switch the flag in linux64Gcc/c++ (or equivalent) in foam-extend-5.0/wmake/rules I have now compiled everything using c++-17 and there was only one fix in NamedEnum. The rest compiles fine. If you wish to use this, please check out the nextRelease branch, as follows: git clone -b nextRelease <blah blah=""> foam-extend-5.0</blah> and compile. Most porting changes are in the nextRelease branch, as we are due for foam-extend-5.0 anyway. Hope this helps, Hrvoje