You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I've been able to install ngsTools in a docker container in the past, but now I'm getting a compilation error in the
ngsUtils/GetSubGeno.cpp file.
A template structure named 'array' is declared in this file and when it is referenced in line 76, the compiler gives an "ambiguous reference" error.
This does not happen when I compile with gcc11 on a different machine but does when I use gcc13 in the docker container.
This is my hypothesis: It appears that there has been a change in the std library that now includes array as a template (std::array). Because of the 'using namespace std' line, the compiler is getting confused about what array template is being referenced. But I'm not a strong c++ programmer so I may be misunderstanding.
This is an issue for me because I am updating my docker containers for HPC usage
Thanks for any perspective
allan
The text was updated successfully, but these errors were encountered:
Hi I've been able to install ngsTools in a docker container in the past, but now I'm getting a compilation error in the
ngsUtils/GetSubGeno.cpp file.
A template structure named 'array' is declared in this file and when it is referenced in line 76, the compiler gives an "ambiguous reference" error.
This does not happen when I compile with gcc11 on a different machine but does when I use gcc13 in the docker container.
This is my hypothesis: It appears that there has been a change in the std library that now includes array as a template (std::array). Because of the 'using namespace std' line, the compiler is getting confused about what array template is being referenced. But I'm not a strong c++ programmer so I may be misunderstanding.
This is an issue for me because I am updating my docker containers for HPC usage
Thanks for any perspective
allan
The text was updated successfully, but these errors were encountered: