ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2018-12-19T11:26:51Zhttps://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/34Request to make change in qt.conf using relocateQT2018-12-19T11:26:29ZPawan GhildiyalRequest to make change in qt.conf using relocateQTHi Mark
As discussed , please change path of **prefix** to installation qt dir
under third party dir .
the file is located inside
> qt-5.9.1/bin/qt.conf
Regards
PawanHi Mark
As discussed , please change path of **prefix** to installation qt dir
under third party dir .
the file is located inside
> qt-5.9.1/bin/qt.conf
Regards
PawanPawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/23Add LLVM_ARC_PATH simular MESA_ARC_PATH2018-12-19T11:26:17ZPawan GhildiyalAdd LLVM_ARC_PATH simular MESA_ARC_PATHSince osmesa is usually build with llvm , it will be better have similar
option for llvm as for mesa i.e in config.sh/vtk add LLVM_ARCH_PATH
similar to MESA_ARCJ_PATHSince osmesa is usually build with llvm , it will be better have similar
option for llvm as for mesa i.e in config.sh/vtk add LLVM_ARCH_PATH
similar to MESA_ARCJ_PATHMark OLESENMark OLESENhttps://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 OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/38script error (makeOPENMPI, v1806)2018-07-05T12:13:02Zsariew8script error (makeOPENMPI, v1806)hi developer!
In $FOAM_ETC/bashrc, i changed L85 from 'SYSTEMOPENMPI' to 'OPENMPI'.
run the script makeOPENMPI but my term said the below
./makeOPENMPI: 60: /home/sariew9/OpenFOAM/OpenFOAM-v1806/etc/config.sh/mpi: _foamEtc: not found
...hi developer!
In $FOAM_ETC/bashrc, i changed L85 from 'SYSTEMOPENMPI' to 'OPENMPI'.
run the script makeOPENMPI but my term said the below
./makeOPENMPI: 60: /home/sariew9/OpenFOAM/OpenFOAM-v1806/etc/config.sh/mpi: _foamEtc: not found
What is the problem?
(under the ubuntu14.04LTS)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/18makeOPENMPI with openmpi-2.1.1 gives configure warning2018-06-28T08:36:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commakeOPENMPI with openmpi-2.1.1 gives configure warningconfigure: WARNING: unrecognized options: --disable-mpi-profileconfigure: WARNING: unrecognized options: --disable-mpi-profileMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/31scotch6.0.5a building2018-06-28T08:31:14ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch6.0.5a buildingdownloaded scotch6.0.5a (https://gforge.inria.fr/frs/?group_id=248), adapted etc/config.sh/scotch for new version. When building it cannot find scotch.h. It works fine if built 'by hand' : first builds dummysizes which then writes scotch.h.downloaded scotch6.0.5a (https://gforge.inria.fr/frs/?group_id=248), adapted etc/config.sh/scotch for new version. When building it cannot find scotch.h. It works fine if built 'by hand' : first builds dummysizes which then writes scotch.h.Mark 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/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/35Request to add additional flag to resolve issue : QFontDatabase: Cannot find...2018-06-07T08:08:28ZPawan GhildiyalRequest to add additional flag to resolve issue : QFontDatabase: Cannot find font directoryIn makeQT
QT has two option either to use system font or use QT font to display fonts
in application build, using QT . I noticed that present makeQT script
is configured to use QT font. It has not caused any issue till now but i not...In makeQT
QT has two option either to use system font or use QT font to display fonts
in application build, using QT . I noticed that present makeQT script
is configured to use QT font. It has not caused any issue till now but i noticed
that with QT-5.9.1 , building with default makeQT script ,cause Paraview to pop
up message "QFontDatabase: Cannot find font directory" and no font appear in QT.
Configuring qt with additional flag ** -**fontconfig** **, resolved the issue.
I did test with SUSE-Enterprise-12SP1 using gcc-6.4.1
Regards
PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/36compile issue with kahip v17122018-05-29T10:49:29ZJed Storeycompile issue with kahip v1712I get the following error trying to build (./Allwmake > log.make 2>&1) the ThirdParty software from v1712:
"make: *** No rule to make target 'Make/linux64GccDPInt64Opt/interface/kaHIP/_interface.cpp.dep', needed by 'Make/linux64GccDPInt...I get the following error trying to build (./Allwmake > log.make 2>&1) the ThirdParty software from v1712:
"make: *** No rule to make target 'Make/linux64GccDPInt64Opt/interface/kaHIP/_interface.cpp.dep', needed by 'Make/linux64GccDPInt64Opt/interface/kaHIP_interface/o' . Stop. Error buidling: kahip.
Not sure if it is relevant, but there were a bunch (~100) of these lines in the kahip part of the log: "make: /opt/OpenFOAM-v1712/wmake/platforms/linux64Gcc/wmkdep: Command not found", though not every line was that.
Also, not sure if it is relevant, but when I source the OpenFOAM bashrc, I get the following warning: "No completion added for /opt/OpenFOAM-v1712/platforms/linux64GccDPInt640Opt/bin".
I also have a problem compiling cfmesh (separate bug report, probably not related?), but besides that and this, everything else seems to compile and work fine.
OF: v1712
OS: CentOS 7.5
Bash: 4.2
GCC: 4.8.5 (system)
cmake: 3.11.2 (manual install system)
Boost: 1.53 (system)Mark 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/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/33compilation with IntelMPI failed2018-05-16T09:29:57ZPawan Ghildiyalcompilation with IntelMPI failedUsing ThirdParty compiler Gcc64 and pointing to MPI_ROOT path to intelMPI
complain about mpi.h not found during compilation .
"sinclude $(GENERAL_RULES)/mplib$(WM_MPLIB)"
"sinclude $(RULES)/mplib$(WM_MPLIB)"
Solution: **Mark** p...Using ThirdParty compiler Gcc64 and pointing to MPI_ROOT path to intelMPI
complain about mpi.h not found during compilation .
"sinclude $(GENERAL_RULES)/mplib$(WM_MPLIB)"
"sinclude $(RULES)/mplib$(WM_MPLIB)"
Solution: **Mark** pointed out following need to be added to fix this issue
"sinclude $(DEFAULT_RULES)/mplib$(WM_MPLIB)"
Regards
PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/32QT installation moved to other location : need more environment variable to b...2018-05-14T13:28:25ZPawan GhildiyalQT installation moved to other location : need more environment variable to be setI need to add following environment variable to make paraview run .
export PYTHONHOME=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7
export PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/bin:$PATH
export LD_LIBRARY_PAT...I need to add following environment variable to make paraview run .
export PYTHONHOME=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7
export PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/bin:$PATH
export LD_LIBRARY_PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/lib/:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/qt-5.9.0/pluginsMark 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/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/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/22OpenMPI: Request to add environment variable or suggest some workaround2017-11-30T19:57:15ZPawan GhildiyalOpenMPI: Request to add environment variable or suggest some workaroundHi Mark,
If OpenMPI installation location is different from where it is compiled,
then it does not allow to run mpirun command . There are two solution of it.
i) Set OPAL_LIBDIR variable to $OPAL_PREFIX/lib64
ii) Change file ...Hi Mark,
If OpenMPI installation location is different from where it is compiled,
then it does not allow to run mpirun command . There are two solution of it.
i) Set OPAL_LIBDIR variable to $OPAL_PREFIX/lib64
ii) Change file in openmpi installation ile lib64/pkgconfig/orte.pc change libdir and prefix to point to
installation .
I prefer , to add new option OPAL_LIBDIR as variable i.e config.sh/mpi
Thanks
PawanMark OLESENMark OLESEN