home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.slackware      I think its the one without Selinux crap      87,272 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 87,187 of 87,272   
   Lew Pitcher to Lew Pitcher   
   Re: Caveats while self-upgrading CUPS   
   31 Oct 25 19:32:21   
   
   From: lew.pitcher@digitalfreehold.ca   
      
   On Fri, 31 Oct 2025 15:07:33 +0000, Lew Pitcher wrote:   
      
   > Hi, guys   
   >   
   > 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. For the   
   > record, I upgraded   
   >  qpdf to v8.3.0 (required by cups-filters),   
   >  cups to Openprinting Cups v2.4.14,   
   >  cups-filters to Openprinting Cups v1.28.16, and   
   >  gutenprint to v5.3.5   
   >   
   > 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".   
   >   
   > 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 recognize that this solution does not represent   
   > the best fix for the problem, andI will pursue a better solution as I   
   > progress in this install.   
      
   OK, I have found a better solution to my library problem. I removed   
   the /usr/lib64 symlinks I used to bypass the problem, and restored the   
   two aaa_elflibs libraries to /usr/lib64 (/usr/lib64/libcups.so.2 and   
   /usr/lib64/libcupsimage.so.2)   
      
   Then I revised my /etc/ld.so.conf to place   
     /usr/local/lib64   
   ahead of   
     /usr/lib64   
   and reran ldconfig.   
      
   This updated the cache so that the dynamic linker will find the   
   /usr/local/lib64 libraries before it finds the /usr/lib64 libraries,   
   and, thus, allows my new, locally-compiled cups libraries to supercede   
   the aaa_elflibs-supplied libraries.   
      
   I'm going to call this problem done for now.   
   --   
   Lew Pitcher   
   "In Skills We Trust"   
   Not LLM output - I'm just like this.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca