ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2019-07-21T22:56:27Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/10Ensure third-party compile of current and upcoming paraview work.2019-07-21T22:56:27ZMark OLESENEnsure third-party compile of current and upcoming paraview work.Adjust patching for 5.1.2 and 5.2.0 (using current release candidate).Adjust patching for 5.1.2 and 5.2.0 (using current release candidate).Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/9Cannot compile paraview32019-07-21T22:56:27ZMark OLESENCannot compile paraview3With paraview 3.14 (Feb 2012) and paraview 3.98 (Dec 2012) experience unresolvable build issues. Can no longer compile (was also the case at the time of the 1606 release).With paraview 3.14 (Feb 2012) and paraview 3.98 (Dec 2012) experience unresolvable build issues. Can no longer compile (was also the case at the time of the 1606 release).Version v1612Mark 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 OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/16makeParaView and makeVTK possibly assume lib64 for mesa libraries2017-09-28T12:04:04ZMark OLESENmakeParaView and makeVTK possibly assume lib64 for mesa librariesexchange platform https://exchange.openfoam.com/node/398
@Pawan @Prashantexchange platform https://exchange.openfoam.com/node/398
@Pawan @PrashantVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/13COMP: Inconsistent files for ADIOS2019-07-21T22:56:27ZPrashant SonakarCOMP: Inconsistent files for ADIOShttps://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain...https://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain `Makefile.in` (has Makefile.am) and gets terminated during compilation.
- The alt download returns `adios-1.11.0` but makeADIOS script expects the folder name in CAPITAL.
@andyVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/28no mpicc on cray2017-12-18T10:05:26ZMark OLESENno mpicc on cray- the cray `cc` handles mpi paths- the cray `cc` handles mpi pathsv1712Mark OLESENMark OLESEN2017-12-18https://develop.openfoam.com/Development/ThirdParty-common/-/issues/27compilation of KaHIP2017-12-12T18:36:51ZMatej Formancompilation of KaHIPrunning `makeKAHIP` run in 2 issues on CentOS (would on anything)
1) downloaded KaHIP_2.00.tar.gz unpacks to KaHIP_v2.00d but `makeKAHIP` requires kahip-2.00 directory
2) compilation stumbles on directory which is already created:
``...running `makeKAHIP` run in 2 issues on CentOS (would on anything)
1) downloaded KaHIP_2.00.tar.gz unpacks to KaHIP_v2.00d but `makeKAHIP` requires kahip-2.00 directory
2) compilation stumbles on directory which is already created:
```
cpptoo: cycle_search.cpp
cpptoo: cycle_refinement.cpp
cpptoo: tabu_search.cpp
mkdir: cannot create directory ‘/home/linux/OpenFOAM/ThirdParty-plus/platforms/linux64GccDPInt32/lib’: File exists
make: *** [/home/linux/OpenFOAM/ThirdParty-plus/platforms/linux64GccDPInt32/lib/libkahip.so] Error 1
Error building: kahip
```v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/26ThirdParty-plus FFTW version2018-12-19T11:26:51ZRoger AlmenarThirdParty-plus FFTW versionThe FFTW version that we have in our develop files (etc/config.sh/FFTW) has been withdrawn from the public domain.
See from www.fftw.org/release-notes.html:
FFTW 3.3.6-pl1 (withdrawn)
Jan 16th, 2017
Bugfix: FFTW 3.3.6 had the wrong...The FFTW version that we have in our develop files (etc/config.sh/FFTW) has been withdrawn from the public domain.
See from www.fftw.org/release-notes.html:
FFTW 3.3.6-pl1 (withdrawn)
Jan 16th, 2017
Bugfix: FFTW 3.3.6 had the wrong libtool version number, and generated shared libraries of the form libfftw3.so.2.6.6 instead of libfftw3.so.3.*.
We should probably move to -pl2 instead of –pl1 .v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/25Note : option few syntax correction for compiling openmpi :makeOPENMPI2017-12-15T16:34:48ZPawan GhildiyalNote : option few syntax correction for compiling openmpi :makeOPENMPINote: In version openmpi-3.0.0, **--with-verbs-dir**
replaced **--with-verbs-libdir**Note: In version openmpi-3.0.0, **--with-verbs-dir**
replaced **--with-verbs-libdir**v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/24QT : adding path to QT environement2018-05-29T10:43:47ZPawan GhildiyalQT : adding path to QT environementHi
We needs QT for paraview compilation. makeQT script
allow compilation in nice way and then makeParaview
does all compilation in nice way. However i see problem
in using paraview if i moved my installation area to other locati...Hi
We needs QT for paraview compilation. makeQT script
allow compilation in nice way and then makeParaview
does all compilation in nice way. However i see problem
in using paraview if i moved my installation area to other location
. I need to manually set QT lib path as well QT_PLUGIN_PATH.
Can we make something similar vtk script for QT which will set desired
environment variable . If there is some other of doing same, please
highlight it .
Thanks
Pawanv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/37makeParaview - BUILD_SUFFIX2018-06-11T09:48:04ZPrashant SonakarmakeParaview - BUILD_SUFFIX- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* ins...- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* instead of \*qt\*, which leads to failure in setting up Qt5_DIR, needed for building PVReaders.
using qt-5.6.3 and ParaView-5.5.0v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/30Check for wmake toolchain in some third-party components2018-06-28T08:31:14ZMark OLESENCheck for wmake toolchain in some third-party componentsIf ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
If ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/29more stringency when exporting WM_ compiler settings2018-05-29T10:42:24ZMark OLESENmore stringency when exporting WM_ compiler settings- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env...- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env sets ThirdParty Clang (setting WM_CC in the process), but this is the component we are trying to build, so `makeLLVM` will have problems configuring for this non-existent compiler.
1. can avoid this by using `makeLLVM -gcc` to force use of gcc for making Clang. This seems to be an ok alternative, since this isn't part of the normal OpenFOAM process (we are building the toolchain for building OpenFOAM).
2. check within the ThirdParty scripts that the exported `CC` variable corresponds to a command. Eg,
if test -n "$WM_CC" && command -v "$WM_CC" >/dev/null
then
export CC="$WM_CC"
[ -n "$WM_CFLAGS" ] && export CFLAGS="$WM_CFLAGS"
fi
Probably the second one is OK to include too, but targeted for the next release.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/53Paraview- with python and openmpi>42020-07-09T15:11:49ZPrashant SonakarParaview- with python and openmpi>4Placeholder to resolve issues when building
- Paraview-5.6.3
- Python-2.7
- Openmpi-4.0.3
This fails with mp4py issue as reported in https://gitlab.kitware.com/vtk/vtk/-/issues/17544
We might need a patch for 5.6.3 version or upgrade t...Placeholder to resolve issues when building
- Paraview-5.6.3
- Python-2.7
- Openmpi-4.0.3
This fails with mp4py issue as reported in https://gitlab.kitware.com/vtk/vtk/-/issues/17544
We might need a patch for 5.6.3 version or upgrade to new Paraview ??
@mark @andyv2012https://develop.openfoam.com/Development/ThirdParty-common/-/issues/67Introducing MUI code coupling library into OpenFOAM2024-03-27T16:38:12ZWendi LiuIntroducing MUI code coupling library into OpenFOAM## Functionality to add/problem to solve
Integrate the code coupling library [Multiscale Universal Interface](https://mxui.github.io/) in OpenFOAM as a third-party library to couple OpenFOAM with other solvers or OpenFOAM with itself.
...## Functionality to add/problem to solve
Integrate the code coupling library [Multiscale Universal Interface](https://mxui.github.io/) in OpenFOAM as a third-party library to couple OpenFOAM with other solvers or OpenFOAM with itself.
## Target audience
Users who want to couple OpenFOAM with other solvers or OpenFOAM with itself.
## Proposal
A working general integration of MUI is proposed by applying the following patch to the ThirdParty repository.
[muiIntegrationTP.patch](/uploads/9b0637fcc8137a818b65f31875d6e40f/muiIntegrationTP.patch)
Below is a summarise of what have been added and modified.
- Modified `Allwmake` to include script to build MUI.
- Added build script `makeMUI.`
- Added MUI related patch file `etc/patches/MUI-2.0` to resolve ambiguity issue between MUI-v2.0 and OpenFOAM. We have merged the changes into the MUI repository, so that no patch files will be needed in future MUI releases.
- Updated `BUILD.md` and `SOURCES.md` to include MUI related documentations.
## Related issue
[openfoam issue #3127](https://develop.openfoam.com/Development/openfoam/-/issues/3127)
## What does success look like, and how can we measure that?
The Patch has been tested with the ThirdParty development repository (commit 7ff69fa1a733b45b069a387fd0c275b15b7f2150).
The proposed changes can be patched and tested as follows
- Clone Development Repositories
```
git clone https://develop.openfoam.com/Development/ThirdParty-common.git
git clone https://develop.openfoam.com/Development/openfoam.git
```
- Obtain the MUI source file in the ThirdParty Repository
```
cd ThirdParty-common/sources
mkdir mui && cd mui
wget https://github.com/MxUI/MUI/archive/refs/tags/2.0.tar.gz
tar -xf 2.0.tar.gz && rm 2.0.tar.gz
```
- Obtain and place patches in Repositories
- Patch
```
cd openfoam/
patch -p2 < muiIntegrationOF.patch
rm muiIntegrationOF.patch
cd ../ThirdParty-common/
patch -p2 < muiIntegrationTP.patch
rm muiIntegrationTP.patch
```
- Change permission of newly added files if needed
- Enable MUI support (MUI is disabled by default)
- Modify L37 of `openfoam/etc/config.sh` to change `mui_version=MUI-none` into `mui_version=MUI-2.0`
- Source and Allwmake
```
cd openfoam/
source etc/bashrc
./Allwmake -j 4
```
- Test MUI enabled OpenFOAM
```
cd openfoam/applications/test/coupling-MUI
./testCase/Allrun
cd openfoam/tutorials/basic/laplacianFoamMUI
./AllrunCoupled
```
If MUI library successfully integrated, the following log messages can be found for the `coupling-MUI` unit test.
```
...
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mesh for time = 0
```
If MUI library successfully integrated, the following log messages can be found for the `laplacianFoamMUI` tutorial.
```
....
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_twoD_1" as 59a4e385
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_twoD_1" as 59a4e385
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_twoD_1 [59a4e385] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_twoD_1, Domain size: 2, Peers: 2
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 1, "domain1" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 0, "domain1" registered interface "interface_threeD_1" as 31f80b7e
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_threeD_1 [31f80b7e] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_threeD_1, Domain size: 2, Peers: 2
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 1, "domain1" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 0, "domain1" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_T_1" as 4a5523ab
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_T_1 [4a5523ab] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_T_1, Domain size: 2, Peers: 2
Calculating temperature distribution
Calculating temperature distribution
Time = 0.005
Time = 0.005
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 0
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 0
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 0
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 0
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 0
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 0
DICPCG: Solving for T, Initial residual = 1, Final residual = 8.33243e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00446911, Final residual = 7.14892e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 0.000148123, Final residual = 6.63323e-07, No Iterations 2
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 0
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 0
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 0
ExecutionTime = 0.07 s ClockTime = 0 s
Time = 0.01
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 1
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 1
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 1
DICPCG: Solving for T, Initial residual = 0.203755, Final residual = 1.57027e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00184337, Final residual = 2.32416e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 1, Final residual = 8.33243e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 5.70921e-05, Final residual = 2.8776e-07, No Iterations 2
DICPCG: Solving for T, Initial residual = 0.00446911, Final residual = 7.14892e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 0.000148123, Final residual = 6.63323e-07, No Iterations 2
MUI interface "domain2"/"interface_twoD_1" value fetched: 1 at Iteration = 0
MUI interface "domain2"/"interface_threeD_1" value fetched: 2 at Iteration = 0
MUI interface "domain2"/"interface_T_1" value fetched: 3 at Iteration = 0
ExecutionTime = 0.1 s ClockTime = 0 s
Time = 0.01
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 1
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 1
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 1
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 1
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 1
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 1
ExecutionTime = 0.08 s ClockTime = 0 s
Time = 0.015
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 2
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 2
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 2
DICPCG: Solving for T, Initial residual = 0.109922, Final residual = 4.92455e-07, No Iterations 6
DICPCG: Solving for T, Initial residual = 0.00104616, Final residual = 7.0666e-07, No Iterations 3
DICPCG: Solving for T, Initial residual = 3.13839e-05, Final residual = 1.66653e-07, No Iterations 2
DICPCG: Solving for T, Initial residual = 0.203755, Final residual = 1.57027e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00184337, Final residual = 2.32416e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 5.70921e-05, Final residual = 2.8776e-07, No Iterations 2
MUI interface "domain2"/"interface_twoD_1" value fetched: 1 at Iteration = 1
MUI interface "domain2"/"interface_threeD_1" value fetched: 2 at Iteration = 1
MUI interface "domain2"/"interface_T_1" value fetched: 3 at Iteration = 1
ExecutionTime = 0.11 s ClockTime = 1 s
Time = 0.015
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 2
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 2
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 2
DICPCG: Solving for T, Initial residual = 0.109922, Final residual = 4.92455e-07, No Iterations 6
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 2
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 2
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 2
ExecutionTime = 0.1 s ClockTime = 1 s
...
```https://develop.openfoam.com/Development/ThirdParty-common/-/issues/66When I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS...2023-01-27T11:19:57ZJuan Díaz GonzálezWhen I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an errorWhen I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an error.
The error that I have is this:
`[ 46%] Building C object testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/TestUtilsCWri...When I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an error.
The error that I have is this:
`[ 46%] Building C object testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/TestUtilsCWriter.c.o`
[ 46%] Building C object testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/PerfManyVars.c.o`
[ 46%] Linking C executable ../../../bin/Test.Utils.CWriter`
[ 46%] Linking C executable ../../../../bin/PerfManyVars`
`/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-redhat-linux/8//libstdc++_nonshared.a(functexcept48.o): undefined reference to symbol '__cxa_free_exception@@CXXABI_1.3'`
`/usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line`
`make[2]: *** [testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/build.make:99: bin/Test.Utils.CWriter] Error 1`
`make[1]: *** [CMakeFiles/Makefile2:8571: testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/all] Error 2`
`make[1]: *** Waiting for unfinished jobs....`
`/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-`redhat-linux/8//libstdc++_nonshared.a(functexcept48.o): undefined reference to symbol '__cxa_free_exception@@CXXABI_1.3'`
`/usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line`
make[2]: *** [testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/build.make:99: bin/PerfManyVars] `Error 1`
`make[1]: *** [CMakeFiles/Makefile2:8253: testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/all] Error 2`
`[ 46%] Linking CXX executable ../../bin/adios2_reorganize_mpi`
`[ 46%] Built target adios_reorganize_mpi`
`[ 46%] Linking CXX executable ../../bin/bpls`
`[ 46%] Built target bpls`
`[ 46%] Linking CXX shared library ../../lib64/libadios2_cxx11.so`
`[ 46%] Built target adios2_cxx11`
`make: *** [Makefile:146: all] Error 2`
`Error building: ADIOS2-2.8.3`https://develop.openfoam.com/Development/ThirdParty-common/-/issues/65Incorrect download links for METIS during compilation2022-08-04T14:44:02ZDanyal MohaddesIncorrect download links for METIS during compilation# Summary
The download links for METIS provided during ThirdParty compilation are out of date.
# Steps to Reproduce
1. Download the latest version of ThirdParty (v2206)
2. `./Allwmake`
# Current Behavior
When METIS compilation is reach...# Summary
The download links for METIS provided during ThirdParty compilation are out of date.
# Steps to Reproduce
1. Download the latest version of ThirdParty (v2206)
2. `./Allwmake`
# Current Behavior
When METIS compilation is reached (and skipped), the links provided to download METIS are to [this link](http://glaros.dtc.umn.edu/gkhome/metis/metis/overview) and [this link](http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz). These links are out of date; the package has since moved.
# Correct Behavior
The link provided to download METIS should be [this one](https://github.com/KarypisLab/METIS).
# Possible fix
Update the links in `BUILD.md`https://develop.openfoam.com/Development/ThirdParty-common/-/issues/64Paraview:5.10.0: catalyst building issue2022-08-04T11:32:33ZPawan GhildiyalParaview:5.10.0: catalyst building issueHi ,
I am using latest release paraview as updated in sourceforge 5.10.0 release.
Build paraview successfully using mesa-llvm and it compiled well.
runTimepostprocessing : compiles well and work well. However catalyst
fail t...Hi ,
I am using latest release paraview as updated in sourceforge 5.10.0 release.
Build paraview successfully using mesa-llvm and it compiled well.
runTimepostprocessing : compiles well and work well. However catalyst
fail to compile with following error. (Note this issue is not there with Paraview-5.10.RC2)
![image](/uploads/b377779ef8b2fda54268a1761d94008a/image.png)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/63build problems with Paraview-5.10 and gcc482021-12-31T13:28:05ZPrashant Sonakarbuild problems with Paraview-5.10 and gcc48Various problems noted (probably not to be fixed) and workarounds to get it compilingVarious problems noted (probably not to be fixed) and workarounds to get it compilinghttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/62Cgal/boost does not properly set -toolset parameter when using non gcc compiler.2021-12-15T18:39:06ZFelix LeClairCgal/boost does not properly set -toolset parameter when using non gcc compiler.When etc/bashrc has wm_compiler set to use the intel compiler suite (Icc), and wmake all | ./Allmake is called, cgal and boost do no have the -toolset variable set to pass -toolset=intel-linux to makeCGAL.
related to bootsrap.sh is tha...When etc/bashrc has wm_compiler set to use the intel compiler suite (Icc), and wmake all | ./Allmake is called, cgal and boost do no have the -toolset variable set to pass -toolset=intel-linux to makeCGAL.
related to bootsrap.sh is that it does not seem to pass 'openmpi yes ;' causing performance degradations