>> home/elfring/Projekte/Bau/Evolution/3.36.5/Probe/bin/evolution: >> symbol lookup error: /usr/lib64/libwebkit2gtk-4.0.so.37: undefined >> symbol: wpe_fdo_initialize_shm > > Hi, > I've not much idea on this one.
I got further software development ideas accordingly. > On the first look, it looks like a > mismatch of the development files and the binary files, or stale build > artifacts (then you might eventually rebuild), or some dependency > (possibly of the WebKitGTK) is old/new, or... You may ask Google or > your distribution maintainer, I became curious about software evolution also around calls of the function “wpe_fdo_initialize_shm”. > though the quickest workaround is obvious, revert the package(s) update. Maybe. Would anybody like to take any other software design options into account? How are the chances to try software build configurations out with less WebKit functionality? Regards, Markus _______________________________________________ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers