-
Notifications
You must be signed in to change notification settings - Fork 8
Release/2.7.5 #30
New issue
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
Release/2.7.5 #30
Conversation
…mpilation error on codac side
@SimonPinches just pushed the same fix for server2. |
Thanks @jholloc - all works now :-) |
Compilation fails with Intel compilers (see IMAS-5014):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we fix to also build with Intel compilers?
Still have problems compiling with Intel:
|
Not sure what we can do about the latest issue... looks like the Intel compiler doesn't like the GSL library, which is out of our control. I think this library is currently only used in the UDA CLI, so we could just turn of CLI compilation for Intel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not better with last commit :-(
/home/ITER/hoeneno/GIT/UDA/extlib/GSL-4.0.0/include/gsl/span(128): error #597: "gsl::details::span_iterator<Type>::operator gsl::details::span_iterator<const int64_t={__int64_t={signed long}}>() const noexcept [with Type=const int64_t={__int64_t={signed long}}]" will not be called for implicit or explicit conversions
explicit constexpr operator span_iterator<const Type>() const noexcept
^
detected during:
instantiation of class "gsl::details::span_iterator<Type> [with Type=const int64_t={__int64_t={signed long}}]" at line 633
instantiation of "gsl::span<ElementType, Extent>::iterator gsl::span<ElementType, Extent>::begin() const noexcept [with ElementType=const int64_t={__int64_t={signed long}}, Extent=18446744073709551615UL]" at line 85 of "/home/ITER/hoeneno/GIT/UDA/source/serialisation/capnp_serialisation.cpp"
instantiation of "std::ostream &operator<<(std::ostream &, gsl::span<T, 18446744073709551615UL>) [with T=const int64_t={__int64_t={signed long}}]" at line 120 of "/home/ITER/hoeneno/GIT/UDA/source/serialisation/capnp_serialisation.cpp"
instantiation of "void print_data<T>(std::ostream &, TreeNode::Array::Reader &, const std::string &) [with T=int64_t={__int64_t={signed long}}]" at line 158 of "/home/ITER/hoeneno/GIT/UDA/source/serialisation/capnp_serialisation.cpp"
@jholloc trying some tricks I got from https://community.intel.com/t5/Intel-C-Compiler/Error-operator-will-not-be-called-for-implicit-or-explicit/td-p/1025378 it seems that I can continue the compilation with
I also have later another compilation error:
|
… (required for putting data, added getErrorMsg to print any errors from the handle
Thanks @jholloc , now I get the next error (but this one looks easier to fix):
|
@SimonPinches I've hopefully removed those warnings for the Intel compiler. |
Still fails with same error :-(
|
I've found https://estuarine.jp/2021/03/install-oneapi which gives details of installing the Intel compilers on Ubuntu. I'll try this on my local VM and if it works i'll set up an Intel CI build. |
@SimonPinches i've added an Intel CI build and made the required fixes to get the Intel build working. |
Thanks. I'll give it a try as soon as I get a chance. |
Thanks @jholloc. I confirm this now works for our intel/2023b toolchains on RHEL9 and so will approve this PR again :-) |
UKAEA client and server builds and tests pass |
Addressing issues with SSL. Also adding running of UDA integration tests to CI, including running tests with SSL authenticated client/server.
Fixing issues: