NERSCPowering Scientific Discovery Since 1974

Intel uses very old version of libstdc++ by default [updated]

January 15, 2014 by Mike Stewart, NERSC USG (3 Comments)

Status:   Reported to Cray as case 84319, became bug 806610.

Updated October 13, 2014 by Scott French, NERSC USG

When PrgEnv-intel is loaded, the Intel compiler gets libstdc++ from on the default environment on the login node, which is typically quite old. This test case illustrates the problem on Edison:

> cat TestLibVersion.C 
#include <iostream>
int main()
{
std::cout<<"libstdc++ version is "<< __GLIBCXX__ << std::endl;
}
> CC -o libver -std=c++11 TestLibVersion.C
> ./libver
libstdc++ version is 20091019

The workaround suggested by Cray is to load a recent version of the GNU compilers (i.e. the gcc module, not the PrgEnv-gnu module), which adds the newer libstdc++ to the environment and makes it accessible to Intel.  For example, on Edison:

> module load gcc/4.9.1
> CC -o libver -std=c++11 TestLibVersion.C
> ./libver
libstdc++ version is 20140716

Post your comment

You cannot post comments until you have logged in. Login Here.

Comments

  • Hi Mike, is there an update/workaround on this? This seems to be an issue also on computational nodes. Thank you, Matus

    Posted by Matus Martini, 26/02/2014 4:01pm (8 months ago)

  • Hi,

    Is there a recommended solution for this ?

    My mpich2 compiled with Intel ( I did do "module swap PrgEnv-pgi PrgEnv-intel") has got errors (when I "aprun" on it) :

    error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory


    Kin

    Posted by Kin Yip, 31/01/2014 11:30am (9 months ago)

  • Hi,

    Is there a recommended solution for this ?

    My mpich2 compiled with Intel ( I did do "module swap PrgEnv-pgi PrgEnv-intel") has got errors (when I "aprun" on it) :

    error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory


    Kin

    Posted by Kin Yip, 31/01/2014 11:28am (9 months ago)

RSS feed for comments on this page | RSS feed for all comments