Open mikhailnov opened 4 years ago
(in case of BricsCAD libz was bundled and was LD_PRELOAD'ed (seems that they did not hear about RPATH or could not use it for some reasons; after that system libpng tried to use that bundled preloaded libz)
Thanks for your report @mikhailnov.
So you suggest to remove libz.so.1
from the excludelist?
If you use system libfreetype, you must use system libpng also as far as I can imagine what is happening
So add libpng16.so.16
to the excludelist, so that it gets bundled?
probably yes, and also libpng12.so.12
Thank you for the suggestion, will do some experiments with it and in case it doesn't have negative effects, add it.
Everyone, feel free to comment.
Thank you very much.
libpng changes soname and ABI too often and there are no guarantee that libpng16 will be in the system
libpng changes soname and ABI too often and there are no guarantee that libpng16 will be in the system
Yes, this is an indication that we should indeed privately bundle it then.
Something similar happened with the old libpng12
I think that https://github.com/AppImage/pkg2appimage/blob/master/excludelist is not very correct.
but you suggest to use it with bundled libpng and libbz2 (note that different distros have incompatible so names of libz2: some have
libbz2.so.1
, but some (Debian, Ubuntu) havelibbz2.so.1.0
)P.S. libharfbuzz depends from libfreetype: