From: Henrik.Carlqvist@deadspam.com   
      
   On Fri, 07 Feb 2025 19:18:37 +0000, root wrote:   
   > I was blown away by the reluctance of the current version of the gcc   
   > compiler:14.2.0. The 15.0 compiler version is 11.2.0 which compiles all   
   > my C programs without a problem.   
      
   During the years, I have at a few occasions seen newer C standards break   
   existing code. When it comes to C++ that seems even more common.   
      
   I haven't tried Slackware current or gcc 14.2.0, but during the years, at   
   some occasions minor fixes has been done to code to make it work with   
   newer compilers. However, often I have not cared to update old code and   
   instead given some argument like -std=gnu90 to use an older C standard   
   than the default in the installed GCC.   
      
   > So I decided to go back to 15.0 and install another kernel alongside   
   > that of 15.0. I pulled down the 6.12.12 kernel from kernel.org. After   
   > tweaking around a bit I got grub to load that kernel, and now I can get   
   > X to start.   
      
   Even with a non standard kernel, running a stable version of Slackware   
   might have its advantages. The updates to 15.0 are only a few security   
   updates a week as opposed to current where any update might break the   
   system that you are beta testing. However, there will probably come a day   
   when you want to upgrade to something like Slackware 15.1 stable. That   
   day you will have to choose between making a recent compiler work with   
   your existing code or installing an older gcc version. If you choose to   
   install an older version of gcc I would advice to install that alongside   
   the original Slackware gcc compiler. You could put your custom compiler   
   below /usr/local or /opt.   
      
   regards Henrik   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)