%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
#Teemu Ollakka Nov 17th, 2020: # SONAME is useful only for libraries which are intended to be linked # against, but not so much for libraries which are loaded dynamically # during runtime. # # Debian policy about shared libraries: # https://www.debian.org/doc/debian-policy/ch-sharedlibs.html # # "Shared libraries that are internal to a particular package or that are # only loaded as dynamic modules are not covered by this section and are # not subject to its requirements." # # This seems also be the approach CMake has taken, see for example # https://stackoverflow.com/a/42186654 galera-4: sharedobject-in-library-directory-missing-soname [usr/lib/libgalera_smm.so]