You are not logged in.
In https://bbs.archlinux.org/viewtopic.php?id=305329 an issue with canon drivers was found that can be solved by installing libxml2-legacy .
I've checked a clean build of cnrdrvcups-lb 1:6.10.1.01-1 and found this :
cnrdrvcups-lb W: Referenced library 'libxml2.so.2' is an uninstalled dependency (needed in files ['usr/lib/libcanonufr2r.so.1.0.0', 'usr/bin/cnpkbidir'])
Building against libxml2-legacy doesn't gives this warning .
$ pacman -Ql libxml2 | grep libxml2.so
libxml2 /usr/lib/libxml2.so
libxml2 /usr/lib/libxml2.so.16
libxml2 /usr/lib/libxml2.so.16.0.2
$
$ pacman -Ql libxml2-legacy | grep libxml2.so
libxml2-legacy /usr/lib/libxml2-legacy/lib/libxml2.so
libxml2-legacy /usr/lib/libxml2-legacy/lib/libxml2.so.2
libxml2-legacy /usr/lib/libxml2.so.2
libxml2-legacy /usr/lib/libxml2.so.2.13.8
$
Apparently the soname-scheme used in libxml2 has changed dramatically .
I can ofcourse change deps from libxml2 to libxml2-legacy , but is there a better solution ?
Last edited by Lone_Wolf (2025-05-07 07:50:31)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Is this a package pulling upstream binaries? Then change the dep. Is this a package building from source? Then build it against the new lib.
Online
The cnrdrvcups-lb PKGBUILD is a mix of opensource & binary code.
libcanonufr2r.so.1.0.0 and cnpkbidir are proprietary binaries and have problems with the new libxml2 .
(other parts are fine with it)
Canon tests the driver on supported *nix versions (prinarily debian & redhat stable versions).
Issues with the driver can be caused by differences between archlinux & debian/redhat packaging source builds, stuff done in the proprietary parts and have other causes.
Building against the new libxml2 breaks hard for atleast 2 printer models, I was hoping changes to the build can solve the issue.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
libxml2 2.14 is actively soname/ABI incompatible as far as I've seen, so using libxml2-legacy is correct until Canon rebuilds their blobs with the new libxml2 version
Since that just came out, it will probably be a while until this trickles down to Ubuntu/Debian and in the interim it's probably simpler to just depend on legacy.
Last edited by V1del (2025-05-06 10:53:20)
Online
Thanks for the input, Scimmia & V1del .
I uploaded cnrdrvcups-lb 1:6.10.1.01-2 to aur which depends on libxml2-legacy .
Marking as Solved.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline