ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2023-06-26T13:36:53Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/61paraview openfoam reader does not like symbolic dimensions2023-06-26T13:36:53ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview openfoam reader does not like symbolic dimensionsWith symbolic dimensions (`writeUnits` in `etc/controlDict`) it will write the dimensions for a dimless field as:
```
dimensions [];
```
This crashes the built-in openfoam reader:
```
[paraview ] vtkOpenFOAMReader.cxx:7184 ...With symbolic dimensions (`writeUnits` in `etc/controlDict`) it will write the dimensions for a dimless field as:
```
dimensions [];
```
This crashes the built-in openfoam reader:
```
[paraview ] vtkOpenFOAMReader.cxx:7184 ERR| vtkOpenFOAMReaderPrivate (0x55cbc0ba2f70): Error reading line 18 of CAEME_AutoGapClosure/15/cellToZone: Expected a number, found a non-digit character ]
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/60script updates2021-03-29T10:24:25ZMark OLESENscript updates- scripts need updates for newer mesa, paraview etc.
@Prashant- scripts need updates for newer mesa, paraview etc.
@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/59Change default WM_NCOMPPROCS2021-03-23T16:55:17ZGuanyang XueChange default WM_NCOMPPROCSI was warned by the HPC manager that the third party make script uses all CPU cores in the head node.
Could you please consider adding a script to change the default behavior if it detects HPC environment?
For example, run `lscpu | gre...I was warned by the HPC manager that the third party make script uses all CPU cores in the head node.
Could you please consider adding a script to change the default behavior if it detects HPC environment?
For example, run `lscpu | grep Socket`. If the result is 2, ask the user if it's in HPC environment, then type in no. of cores (most HPC managers are OK with `-j 4`).https://develop.openfoam.com/Development/ThirdParty-common/-/issues/58build optimized version of PETSc by default?2020-12-23T09:30:56Zstefano zampinibuild optimized version of PETSc by default?Currently, https://develop.openfoam.com/Development/ThirdParty-common/-/blob/master/makePETSC configures PETSc in debug mode.
We should add `--with-debugging=0` unless some openFOAM debug build variable is on. PETSc will be up to 10x fas...Currently, https://develop.openfoam.com/Development/ThirdParty-common/-/blob/master/makePETSC configures PETSc in debug mode.
We should add `--with-debugging=0` unless some openFOAM debug build variable is on. PETSc will be up to 10x faster in non-debug mode. @mark ?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/57better support for cross-compiling2020-08-14T04:42:48ZMark OLESENbetter support for cross-compilingMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/56ADIOS recompiles although already compiled2020-08-18T15:51:01ZHÃ¥kanADIOS recompiles although already compiled### Summary
ADIOS recompiles although already compiled
### Steps to reproduce
Follow the installation procedure of v2006. The problem is in the file https://sourceforge.net/projects/openfoam/files/v2006/ThirdParty-v2006.tgz. Running ....### Summary
ADIOS recompiles although already compiled
### Steps to reproduce
Follow the installation procedure of v2006. The problem is in the file https://sourceforge.net/projects/openfoam/files/v2006/ThirdParty-v2006.tgz. Running ./Allwmake several times, it is not noted that ADIOS is already compiled, so it compiles again. The problem is that the check if it is installed looks for a lib64 directory, while the compilation of ADIOS creates a lib directory. It can be fixed by:
pushd $ADIOS2_ARCH_PATH; ln -s lib lib64; popd
However, it would be better if the test is modified to do it correctly, or if the ADIOS compilation produces a lib64 directory directly.
### Example case
See above
### What is the current *bug* behaviour?
ADIOS recompiles although already compiled
### What is the expected *correct* behavior?
ADIOS should not be compiled if it is already compiled.
### Relevant logs and/or images
The Allwmake command gives output that ADIOS is recompiled.
### Environment information
- OpenFOAM version : v2006
- Operating system : Ubuntu 20.04
- Hardware info : N/A
- Compiler : N/A
### Possible fixes
makeAdios2, line 30:
if [ -d "$dir/include" -a -r "$dir/lib$WM_COMPILER_LIB_ARCH/libadios2$EXT_SO" ]
The $WM_COMPILER_LIB_ARCH needs to be removed, or the problem needs to be fixed some other way.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/55remove libz dependency for scotch2020-08-07T12:18:46ZMark OLESENremove libz dependency for scotch- compression handling is only useful for reading in graph files, which we don't use. Removing it reduces the number of ThirdParty interdependencies.
@Prashant- compression handling is only useful for reading in graph files, which we don't use. Removing it reduces the number of ThirdParty interdependencies.
@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/54handle Fujitsu version of mpicc2021-03-22T14:12:57ZMark OLESENhandle Fujitsu version of mpiccas noted in https://develop.openfoam.com/Development/openfoam/-/issues/1671
- mpifcc vs mpicc
- mpiFCC vs mpicxx
@t-karatsuas noted in https://develop.openfoam.com/Development/openfoam/-/issues/1671
- mpifcc vs mpicc
- mpiFCC vs mpicxx
@t-karatsuMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/52paraview building2021-04-17T08:04:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview building@mark to pull in the requirements can we rephrase as something:
openSUSE
The easiest way of obtaining Paraview is to install the binary version:
```
sudo zypper install paraview-devel
```
Unfortunately this does not install enough to...@mark to pull in the requirements can we rephrase as something:
openSUSE
The easiest way of obtaining Paraview is to install the binary version:
```
sudo zypper install paraview-devel
```
Unfortunately this does not install enough to build our paraFoam reader. However installing above should pull in all the dependencies to build Paraview with our scripts.
If this does not work one can install the dependencies oneselves. The following subset may be enough:
sudo zypper install Mesa-libEGL-devel
sudo zypper install libqt5-qtbase-devel libqt5-qtsvg-devel libqt5-qttools-devel libqt5-qtx11extras
sudo zypper install libXt-devel
```https://develop.openfoam.com/Development/ThirdParty-common/-/issues/50error to compile ./makeParaView2020-06-10T15:52:37ZJoaquin Osseserror to compile ./makeParaViewI'm following all the instruction in the OpenFOAM webpage to install it on Ubuntu 20.04 version
First I did this as the instructions says;
cd $WM_THIRD_PARTY_DIR
./makeParaView
And I received this message;
./makeParaView: 64: local:...I'm following all the instruction in the OpenFOAM webpage to install it on Ubuntu 20.04 version
First I did this as the instructions says;
cd $WM_THIRD_PARTY_DIR
./makeParaView
And I received this message;
./makeParaView: 64: local: -DWM_DP: bad variable name
./makeParaView: 64: -DOPENFOAM: bad variable name
Thankshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/49issues with ptscotch and mingw2020-06-26T08:12:25ZMark OLESENissues with ptscotch and mingwAppears that we might need the following in the Makefile:
```
CCD = gcc -I$(MPI_ARCH_PATH)/include
```
@PawanAppears that we might need the following in the Makefile:
```
CCD = gcc -I$(MPI_ARCH_PATH)/include
```
@PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/48Compilation of paraview5.6.3 does not start.2020-07-22T11:05:07Zsariew8Compilation of paraview5.6.3 does not start.$ ~/OpenFOAM/ThirdParty-common$ ./makeParaView \
./makeParaView: 64: local: -DWM_DP: bad variable name \
./makeParaView: 64: ./makeParaView: -DOPENFOAM: bad variable name
did i make another mistakes?$ ~/OpenFOAM/ThirdParty-common$ ./makeParaView \
./makeParaView: 64: local: -DWM_DP: bad variable name \
./makeParaView: 64: ./makeParaView: -DOPENFOAM: bad variable name
did i make another mistakes?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/46add pkgconfig management/handling to makePETSC2020-06-26T08:05:52ZMark OLESENadd pkgconfig management/handling to makePETSCRelated to suggestion by @szampini - we should address pkgconfig contents when using makePETSC (as per the makeQT handling) to ensure things are movableRelated to suggestion by @szampini - we should address pkgconfig contents when using makePETSC (as per the makeQT handling) to ensure things are movableMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/45warn instead of fail for missing scotch2020-06-26T08:08:24ZMark OLESENwarn instead of fail for missing scotchAs @johan_roenby suggested, warn instead of failing with a missing scotch.
Preferably also provide either a download location or download the required files.As @johan_roenby suggested, warn instead of failing with a missing scotch.
Preferably also provide either a download location or download the required files.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/44cannot build paraview 5.6.0 on OF19062019-07-29T12:31:46Zsariew8cannot build paraview 5.6.0 on OF1906hi developer!
what is the cause of failures like the attached file for the paraview5.6.0 build?
---
ubuntu18.04
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
(Note that the file has about 76.7MB after extraction.)
[log.makePV-0.t...hi developer!
what is the cause of failures like the attached file for the paraview5.6.0 build?
---
ubuntu18.04
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
(Note that the file has about 76.7MB after extraction.)
[log.makePV-0.tar.bz2](/uploads/c1c60c67ef53b1584f8b7693f1676d08/log.makePV-0.tar.bz2)https://develop.openfoam.com/Development/ThirdParty-common/-/issues/43add ospray for paraview2019-03-12T09:47:30ZMark OLESENadd ospray for paraviewMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/42BUG: [to be re-confirmed] : empty directory when using ThirdParty within Open...2019-01-09T10:15:33ZPrashant SonakarBUG: [to be re-confirmed] : empty directory when using ThirdParty within OpenFOAM installation folderWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/41ENH: Mesa- with - llvm2020-06-26T08:09:02ZPrashant SonakarENH: Mesa- with - llvmIn order to compile mesa with llvm (when using gcc), following works
[makeMesa.example](/uploads/f794bf098ab43f344363522d4e81122d/makeMesa.example)
we need
- [x] llvm config enviroment
- [x] mesa compilation in lib64 (presently seem ...In order to compile mesa with llvm (when using gcc), following works
[makeMesa.example](/uploads/f794bf098ab43f344363522d4e81122d/makeMesa.example)
we need
- [x] llvm config enviroment
- [x] mesa compilation in lib64 (presently seem to do in lib for centos7.1)
@markhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/40Building ParaView on opensuse leap 15.0 fails due to qhelpgenerator2018-12-19T11:26:07ZMark OLESENBuilding ParaView on opensuse leap 15.0 fails due to qhelpgeneratorThe normal ParaView macros search for qhelpgenerator manually, not with the cmake components and thus don't find qhelpgenerator-qt5 like it is installed as in leap-15.0
- Discussion: https://discourse.paraview.org/t/building-paraview-5-...The normal ParaView macros search for qhelpgenerator manually, not with the cmake components and thus don't find qhelpgenerator-qt5 like it is installed as in leap-15.0
- Discussion: https://discourse.paraview.org/t/building-paraview-5-5-2-on-opensuse-leap-15-0
- Bug report: https://gitlab.kitware.com/paraview/paraview/issues/18317
- Solution: https://gitlab.kitware.com/paraview/paraview/merge_requests/2608Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/39Cannot build paraview 5.5.2 with gcc 8.1.02018-12-19T11:24:06ZMark OLESENCannot build paraview 5.5.2 with gcc 8.1.0As noted by @Stefan this issue prevents compilation
https://gitlab.kitware.com/third-party/hdf5/merge_requests/1/diffsAs noted by @Stefan this issue prevents compilation
https://gitlab.kitware.com/third-party/hdf5/merge_requests/1/diffsMark OLESENMark OLESEN