We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FYI today I get this error when building OCCA (commit 7add235) on my legacy CentOS 6 machine (64 bit Intel Xeons) using gcc 5.1:
[ 4%] Building CXX object CMakeFiles/libocca.dir/src/core/memoryPool.cpp.o /vol1/vermilion/apps/occa/occa-clone/src/core/memoryPool.cpp:174:55: error: specialization of ‘template<class T> occa::memory occa::experimental::memoryPool::reserve(occa::dim_t)’ in different namespace [-fpermissive] memory memoryPool::reserve<void>(const dim_t entries) { ^ In file included from /vol1/vermilion/apps/occa/occa-clone/include/occa/core/device.hpp:9:0, from /vol1/vermilion/apps/occa/occa-clone/include/occa/core/base.hpp:16, from /vol1/vermilion/apps/occa/occa-clone/src/core/memoryPool.cpp:1: /vol1/vermilion/apps/occa/occa-clone/include/occa/core/memoryPool.hpp:218:18: error: from definition of ‘template<class T> occa::memory occa::experimental::memoryPool::reserve(occa::dim_t)’ [-fpermissive] occa::memory reserve(const dim_t entries); ^ make[2]: *** [CMakeFiles/libocca.dir/src/core/memoryPool.cpp.o] Error 1 make[1]: *** [CMakeFiles/libocca.dir/all] Error 2 make: *** [all] Error 2
BUT note I do not get the error on my more modern Linux Mint 21 machine (64 bit Intel Zeons) using gcc 11.3 (thank goodness!)..
The text was updated successfully, but these errors were encountered:
No branches or pull requests
FYI today I get this error when building OCCA (commit 7add235) on my legacy CentOS 6 machine (64 bit Intel Xeons) using gcc 5.1:
BUT note I do not get the error on my more modern Linux Mint 21 machine (64 bit Intel Zeons) using gcc 11.3 (thank goodness!)..
The text was updated successfully, but these errors were encountered: