(without being able to test it - I'm not an C++ guy, and google's example cases does not do not have an issue with old headerz) Try this: $ module purge; module load DEVELOP gcc/8 ; module load clang ; module load intelmpi This will load Glang after gcc/8 making the headers of latter available fo the Clang compiler. Do NOT 'just load gcc/8' as this would lead to wrong environment. Note that IIRC the Intel compiler have the same issue with later C++ standards (also Intel compiler rely on system headers). Years ago the same state was with c++11 standard... On 01/31/2019 10:21 AM, Marcus Wagner wrote:
Paul, could you have a look?
Best Marcus
On 1/25/19 1:42 PM, Philipp Berger wrote:
Dear list,
apparently the Clang installation is build against the headers of the default GCC 4.8.5, which limits its understanding of C++ to C++11. Would it be possible to at least target the headers of GCC5? That would at least support C++14. Of course, with GCC8.2.0 being available as well, C++17 should also be possible ;)
Kind regards,
Philipp
_______________________________________________ claix18-slurm-pilot mailing list -- claix18-slurm-pilot@lists.rwth-aachen.de To unsubscribe send an email to claix18-slurm-pilot-leave@lists.rwth-aachen.de
-- Marcus Wagner, Dipl.-Inf.
IT Center Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24383 Fax: +49 241 80-624383 wagner@itc.rwth-aachen.de www.itc.rwth-aachen.de
-- Dipl.-Inform. Paul Kapinos - High Performance Computing, RWTH Aachen University, IT Center Seffenter Weg 23, D 52074 Aachen (Germany) Tel: +49 241/80-24915