From: syl@therockgarden.ca   
      
   On 2025-10-31, Lew Pitcher wrote:   
      
   > I'm in the process of upgrading my Slackware 14.2 CUPS service in   
   > order to accommodate my system's new "IPP Everywhere" printer (a   
   > Brother MFC-L8610cdw colour laser printer). As is my standard, I   
   > install self-compiled programs and libraries under the /usr/local   
   > tree, so as to distinguish them from the Slackware provided programs   
   > and libraries found elsewhere, and I did so for this new version of   
   > CUPS. ...   
   > ....   
   > I built these in a "clean room" install of Slackware 14.2 running   
   > under LXC on my development box, and (after some back and forth with   
   > ./configure settings) I managed to get the laser printer to work with   
   > this new version of Cups. However, when I installed these upgrades   
   > (packaged as locally-built Slackware packages), my (hardware)   
   > Slackware 14.2 system would not print, complaining of a cups "filter   
   > failure".   
      
   For what it's worth, on the odd occasion that I might "manually"   
   upgrade a Slackware component that would normally be provided by   
   the OS, I make a point to at least refer to, if not outright use,   
   the original SlackBuild script for that package, adapted, of course,   
   for the new software version that I'm working on installing.  It can   
   easily be adjusted for installing to /usr/local if you insist on   
   that, but with a package normally installed by the OS, and with   
   Slackware-14.2 no longer actively getting updates, I rarely find   
   that using the local installation path is worth it (at least on my   
   own Slackware-14.2 system).   
      
   By using the "official" SlackBuild script, though, you get the   
   package built as it would likely have been done officially (modulo   
   any build-time options you handle differently than was done in the   
   original build script).  If there's any question of how to handle   
   changes in a newer version of the software, it's easy enough to   
   also refer to the SlackBuild script from Slackware-15.0 or -current,   
   and adjust your script accordingly.   
      
   > It turns out that the Slackware aaa_elflibs package includes two   
   > libraries that the Cups package also supplies (/usr/lib64/libcups.so.2   
   > and  /usr/lib64/libcupsimage.so.2), which (as they had regestered in   
   > ld.so.conf ahead of my new libraries) interfered with the proper   
   > execution of the new filters.   
   >   
   > I temporarily worked around this by softlinking those two libraries   
   > to my new libraries in /usr/local/lib64, and managed to properly print   
   > to the new printer. ...   
      
   I agree that adjusting ld.so.conf is a better way to resolve this   
   problem, of course.  I do have to admit to wondering why those two   
   files are even included in aaa_elflibs.  No insight is available from   
   the aaa_elflibs source tree, I'm afraid.   
      
   I hope that I've helped you with whatever your next "manual" package   
   update might be ...   
      
   --   
   ----------------------------------------------------------------------   
   Sylvain Robitaille                                syl@therockgarden.ca   
   ----------------------------------------------------------------------   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)