ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2017-12-15T16:34:48Zhttps://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 OLESENhttps://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/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/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/5Update make script for paraview + python2019-07-21T22:56:27ZMark OLESENUpdate make script for paraview + pythonMark OLESENMark OLESEN