I have found few reports of glibc version 2.28 causing such behaviour (e.g. 
see here <https://bugs.archlinux.org/task/59550>). It might be possible 
that /lib64/ld-linux-x86-64.so.2 on our system "links" to this version of 
glibc. But it actually is a static library:
$ ldd -v ld-linux-x86-64.so.2
statically linked
So there is probably no way to ascertain this. If it infact is so (linked 
to glibc 2.28), then I don't think there is anyway I can get working. With 
a simple code from here <https://stackoverflow.com/a/45107992/8028836>,  I 
have found that my compiler links to glibc version 2.22 both during compile 
and run time. So there is no issue with the compiler.

-- 
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dealii/0c6262f0-e4c1-49da-b896-afc5aa461a50%40googlegroups.com.

Reply via email to