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/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/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/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/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/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/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/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/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/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/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/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/1scotch-6.0.4 build fails2019-07-21T22:56:27ZMark OLESENscotch-6.0.4 build failsSee https://gforge.inria.fr/tracker/index.php?func=detail&aid=19407&group_id=248&atid=1079See https://gforge.inria.fr/tracker/index.php?func=detail&aid=19407&group_id=248&atid=1079Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/2unset shell functions failing in dash2019-07-21T22:56:27ZMark OLESENunset shell functions failing in dashneed "unset -f" instead of a plain "unset" to properly unset functions.
Eg, in makeCGAL
unset -f _foamAddLib ....
@matej @andy need "unset -f" instead of a plain "unset" to properly unset functions.
Eg, in makeCGAL
unset -f _foamAddLib ....
@matej @andy Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/3makeCGAL script not present in ThirdParty-v1606+.tgz2019-07-21T22:56:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commakeCGAL script not present in ThirdParty-v1606+.tgzAllwmake refers to ./makeCGAL but script is not included in pack.Allwmake refers to ./makeCGAL but script is not included in pack.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/4CGAL wmake sets incorrect paths to MPFR and GMP2019-07-21T22:56:27ZSergiy KhanCGAL wmake sets incorrect paths to MPFR and GMPWhen compiling OpenFOAM v1606, the ./makeGcc script gets the MPFR and GMP libraries placed in the lib64/ sub-directory, while `$WM_PROJECT_DIR/wmake/rules/General/CGAL` sets paths explicitly to /lib.
`$ ls -al $WM_THIRD_PARTY_DIR/plat...When compiling OpenFOAM v1606, the ./makeGcc script gets the MPFR and GMP libraries placed in the lib64/ sub-directory, while `$WM_PROJECT_DIR/wmake/rules/General/CGAL` sets paths explicitly to /lib.
`$ ls -al $WM_THIRD_PARTY_DIR/platforms/linux64/gmp-5.1.2
include
lib64
share`
`$ ls -al $WM_THIRD_PARTY_DIR/platforms/linux64/mpfr-3.1.2
include
lib64
share`
`$ cat $WM_PROJECT_DIR/wmake/rules/General/CGAL
CGAL_INC = \
-I$(CGAL_ARCH_PATH)/include \
-I$(MPFR_ARCH_PATH)/include \
-I$(GMP_ARCH_PATH)/include \
-I$(BOOST_ARCH_PATH)/include`
`CGAL_LIBS = \
-L$(MPFR_ARCH_PATH)/lib \
-L$(GMP_ARCH_PATH)/lib \
-L$(BOOST_ARCH_PATH)/lib \
-L$(CGAL_ARCH_PATH)/lib \
-lCGAL \
-lmpfr`
The simple fix is to create symlinks like so:
`$ cd $WM_THIRD_PARTY_DIR
$ (cd platforms/linux64/gmp-5.1.2; ln -s lib64 lib)
$ (cd platforms/linux64/mpfr-3.1.2; ln -s lib64 lib)`Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/5Update make script for paraview + python2019-07-21T22:56:27ZMark OLESENUpdate make script for paraview + pythonMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/6BUG: compilation of scotch-6.0.4 failed2019-07-21T22:56:27ZPrashant SonakarBUG: compilation of scotch-6.0.4 failedscotch-6.0.4 fails to compile with Gcc-4.9.3
Following modification works
LDFLAGS = -Xlinker --no-as-needed $(WM_LDFLAGS) -lz -lm `-lrt`
in etc/wmakeFiles/scotch/Makefile.inc.i686_pc_linux2.shlib-OpenFOAM
@andy @Mattijsscotch-6.0.4 fails to compile with Gcc-4.9.3
Following modification works
LDFLAGS = -Xlinker --no-as-needed $(WM_LDFLAGS) -lz -lm `-lrt`
in etc/wmakeFiles/scotch/Makefile.inc.i686_pc_linux2.shlib-OpenFOAM
@andy @MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/7Allclean script in ThirdParty (v1606+) wrongly deletes all installed ThirdPar...2019-07-21T22:56:27ZPhilippose RajanAllclean script in ThirdParty (v1606+) wrongly deletes all installed ThirdParty packages instead of the out-of-source temporary build filesHello,
The following part of the **Allclean** script in the **ThirdParty** folder of v1606+ wrongly deletes all the *installed* ThirdParty packages instead of deleting only the *out-of-source build* files:
```bash
# clean out-of-source...Hello,
The following part of the **Allclean** script in the **ThirdParty** folder of v1606+ wrongly deletes all the *installed* ThirdParty packages instead of deleting only the *out-of-source build* files:
```bash
# clean out-of-source build directories
[ -d platforms ] && ( set -x; rm -rf platforms/* )
```
Solution:
Change to:
```bash
# clean out-of-source build directories
[ -d build ] && ( set -x; rm -rf build/* )
```
in order to clean only the out-of -source build files, but leave the installed packages intact.
Thank you.
Philippose RajanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/8Build boost/cgal into lib64 on 64-bit systems2019-07-21T22:56:27ZMark OLESENBuild boost/cgal into lib64 on 64-bit systemsNoted as OpenFOAM issue https://develop.openfoam.com/Development/OpenFOAM-plus/issues/288Noted as OpenFOAM issue https://develop.openfoam.com/Development/OpenFOAM-plus/issues/288Version v1612Mark OLESENMark OLESEN