- 06/04/2023 11:31:59 AM (4 months ago)
- 12.0, 12.0-rc1, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/parallelism
- 0f18f2b, 5e61857
- 1 edited
rd4a32f9 r5e7593e 87 87 88 88 <listitem><para>If a package is (directly or indirectly) linked to both 89 the old and new versions of a shared library (for example, the package 89 the old and new s of a shared library (for example, the package 90 90 links to both <filename class='libraryfile'>libfoo.so.2</filename> and 91 91 <filename class='libraryfile'>libbar.so.1</filename>, while the latter 92 92 links to <filename class='libraryfile'>libfoo.so.3</filename>), the 93 93 package may malfunction because the different revisions of the shared 94 library present conflicting locations for some symbol names. This can be 94 library present tions for some symbol names. This can be 95 95 caused by recompiling some, but not all, of the packages linked to the 96 96 old shared library after the package providing the shared library is
Note: See TracChangeset for help on using the changeset viewer.