This blog post explains how to manually work around this issue by placing the correct third party dependencies in the correct location on the target system such that Nektar++ is able to discover and use them during the build process without needing to attempt to download the files.