zhyang-dev/openfoam
1
0
Fork 0
mirror of https://develop.openfoam.com/Development/openfoam.git synced 2025-11-28 03:28:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

DOC: update BuildIssues

Browse Source 
- can compile with icc 17.0.1
- note the min gcc versions needed to compile clang
This commit is contained in:
Mark Olesen
2016-12-22 09:15:13 +01:00
parent 3fc66cb710
commit f4adb1f189
1 changed files with 26 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
BuildIssues.txt
View File

@ -8,8 +8,8 @@ Intel Compiler
-------------- --------------
Since OpenFOAM uses C++11, a fairly recent version is required. Since OpenFOAM uses C++11, a fairly recent version is required.
The Intel compiler - icc (ICC) 17.0.1 20161005 is ok, but the
The Intel compiler - icc (ICC) 17.0.0 20160721 - has a bug that initial release - icc (ICC) 17.0.0 20160721 - has a bug that
will result in these types of error messages. will result in these types of error messages.
MatrixSpaceI.H(492): error: no instance of overloaded function MatrixSpaceI.H(492): error: no instance of overloaded function
@ -17,9 +17,6 @@ Intel Compiler
BRowStart, BColStart>::operator=" matches the specified type BRowStart, BColStart>::operator=" matches the specified type
There is a update patch for the icc compiler to address this bug.
--- ---
VTK VTK
--- ---
@ -28,15 +25,14 @@ If using the runTimePostProcessing to create on-the-fly images, you
can either simply just compile ParaView-5.0.1 and these libraries will can either simply just compile ParaView-5.0.1 and these libraries will
be used. be used.
If you decide to use a separate VTK compilation (for example for If you elect to use a separate VTK compilation (for example for
off-screen rendering), it is advisable to reuse the VTK libraries that off-screen rendering), it is advisable to reuse the VTK libraries that
are provided with ParaView-5.0.1, by making an appropriate symlink are provided with ParaView-5.0.1, by making an appropriate symlink
prior to using makeVTK. This doesn't just reduce diskspace, but works prior to using makeVTK. This doesn't just reduce disk-space, but works
much better than using the VTK-7.1.0.tar file. much better than using the VTK-7.1.0.tar file.
Building runTimePostProcessing with the 'plain' VTK-7.1.0 libraries Using runTimePostProcessing with the 'plain' VTK-7.1.0 libraries does
generally works, but yields odd error and unpleasant looking errors generally work, but does not exit cleanly:
when exiting:
symbol lookup error: .../linux64Gcc/VTK-7.1.0/lib/libvtkCommonExecutionModel-7.1.so.1: symbol lookup error: .../linux64Gcc/VTK-7.1.0/lib/libvtkCommonExecutionModel-7.1.so.1:
undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv undefined symbol: _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv
@ -44,4 +40,24 @@ when exiting:
symbol lookup error: .../linux64Gcc/VTK-7.1.0/lib/libvtkCommonDataModel-7.1.so.1: symbol lookup error: .../linux64Gcc/VTK-7.1.0/lib/libvtkCommonDataModel-7.1.so.1:
undefined symbol: _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev undefined symbol: _ZN49vtkInformationQuadratureSchemeDefinitionVectorKeyD1Ev
This error appears to be suppressed if VTK is compiled with a Debug build-type.
-------------------------
Building on older systems
-------------------------
If the system gcc is too old for building OpenFOAM, a third-party gcc or
clang/llvm installation can be used. If building clang/llvm, note that
there are also minimum gcc/g++ requirements there:
Min gcc/g++
=========== ==========
4.4 llvm-3.4.2
4.7 llvm-3.5.2 - llvm-3.7.0
If your system compiler is too old to build the minimum required gcc or
clang/llvm, it is just simply too old.
-- --