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
Install dependencies for configuration...
Installing known registries into `~/.julia`
julia: symbol lookup error: /opt/hostedtoolcache/julia/1.9.4/x64/bin/../lib/julia/libcurl.so: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
This occurs as soon as the Pkg package is used (instantiate, status, update, ...).
It does not occur when LD_PRELOAD is emptied before. (But then we get the usual HDF5 error.)
Since the last time the CI ran successfully, most notably julia was updated to version 1.9.4.
Along with this, the bundled libcurl went from 4.7.0 to 4.8.0.
The github runner has version 4.7.0 locally installed, which we load via LD_PRELOAD: /lib/x86_64-linux-gnu/libcurl.so.4.
The new bundled libcurl version has several more nghttp2_* symbols.
When Pkg does something, Julia loads the bundled libcurl.so using dlopen. This happens independent of any previously loaded libcurl.
#150 revealed an issue in the CI workflow.
When libtrixi-init-julia is invoked we get:
This occurs as soon as the
Pkg
package is used (instantiate, status, update, ...).It does not occur when
LD_PRELOAD
is emptied before. (But then we get the usual HDF5 error.)Since the last time the CI ran successfully, most notably julia was updated to version 1.9.4.
Along with this, the bundled libcurl went from 4.7.0 to 4.8.0.
The github runner has version 4.7.0 locally installed, which we load via
LD_PRELOAD: /lib/x86_64-linux-gnu/libcurl.so.4
.The new bundled libcurl version has several more
nghttp2_*
symbols.When
Pkg
does something, Julia loads the bundled libcurl.so using dlopen. This happens independent of any previously loaded libcurl.At this point both libcurl.so seem to be loaded
The bundled libcurl contains
nghttp2_*
symbols which are not provided by the system libnghttp2The text was updated successfully, but these errors were encountered: