ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2018-06-28T08:31:14Zhttps://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/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/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/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/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 OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/21makeOPENMPI refers to $infbDIR which does not exist2017-09-28T12:04:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commakeOPENMPI refers to $infbDIR which does not existibLib=$infbDIR/lib$WM_COMPILER_LIB_ARCH
should this be
ibLib=$ibDir/lib$WM_COMPILER_LIB_ARCHibLib=$infbDIR/lib$WM_COMPILER_LIB_ARCH
should this be
ibLib=$ibDir/lib$WM_COMPILER_LIB_ARCHMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/19scotch include file is /usr/include/scotch/scotch.h which does not work in sr...2017-07-20T10:00:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch include file is /usr/include/scotch/scotch.h which does not work in src/parallel/decompose/AllwmakeTest is for $SCOTCH_ARCH_PATH/include/scotch.h or /usr/include/scotch.h
This is on Ubuntu 12.10.Test is for $SCOTCH_ARCH_PATH/include/scotch.h or /usr/include/scotch.h
This is on Ubuntu 12.10.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/17improve support for non-system python locations2017-08-03T06:19:28ZMark OLESENimprove support for non-system python locationsMentioned in https://exchange.openfoam.com/node/424
@PrashantMentioned in https://exchange.openfoam.com/node/424
@PrashantMark 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/15CGAL build includes unneed imageIO2019-07-21T22:56:27ZMark OLESENCGAL build includes unneed imageIOAdds in a possible OpenGL dependency that is not necessary for our purposes. Build issue reported on kubuntu-14.04 (https://www.cfd-online.com/Forums/openfoam-installation/183002-problems-installing-of4-1-kubuntu-14-04-a.html)Adds in a possible OpenGL dependency that is not necessary for our purposes. Build issue reported on kubuntu-14.04 (https://www.cfd-online.com/Forums/openfoam-installation/183002-problems-installing-of4-1-kubuntu-14-04-a.html)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/14inconsistency in fftw make2019-07-21T22:56:27ZMark OLESENinconsistency in fftw makefftw uses double-precision interface only, makeFFTW should not have any special single-precision treatment.
Ref: https://develop.openfoam.com/Development/OpenFOAM-plus/issues/373
@Thalenberghen @Prashantfftw uses double-precision interface only, makeFFTW should not have any special single-precision treatment.
Ref: https://develop.openfoam.com/Development/OpenFOAM-plus/issues/373
@Thalenberghen @PrashantMark 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/12ThirdParty-plus makeLLVM2019-07-21T22:56:27ZRoger AlmenarThirdParty-plus makeLLVMIf you look at line 92, there is a test for variable WM_CC, but then variable CC is set as $WM_CC**X**, different from $WM_CC. Hence in my system it CC is set to empty. The same does not happen with $WM_CXX. Could this be a typo when wri...If you look at line 92, there is a test for variable WM_CC, but then variable CC is set as $WM_CC**X**, different from $WM_CC. Hence in my system it CC is set to empty. The same does not happen with $WM_CXX. Could this be a typo when writing $WM_CC?https://develop.openfoam.com/Development/ThirdParty-common/-/issues/11information about qmake is missing2019-07-21T22:56:27ZJohanna Matsfeltinformation about qmake is missingCannot build paraview because qmake is missing, but no hint about where to find it (would be nice to have).Cannot build paraview because qmake is missing, but no hint about where to find it (would be nice to have).Mark OLESENMark OLESEN