From: pinnerite@gmail.com   
      
   On Sun, 28 Sep 2025 23:46:30 -0400   
   Paul  wrote:   
      
   > On Sun, 9/28/2025 3:35 PM, pinnerite wrote:   
   > > On Sun, 28 Sep 2025 14:30:22 +0100   
   > > Adrian Caspersz  wrote:   
   > >   
   > >> On 28/09/2025 12:37, pinnerite wrote:   
   > >>>   
   > >>> The following warning displayed during a compilation:   
   > >>>   
   > >>> Warning: the compiler differs from the one used to build the kernel   
   > >>>    The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu   
   13.3.0-6ubuntu2~24.04) 13.3.0   
   > >>>    You are using:           gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0   
   > >>>   
   > >>> I cannot clearly make out from synaptic which item to select to overcome   
   this problem   
   > >>>   
   > >>   
   > >> IME Asking Chat-GPT is a valid option when you have error messages like   
   > >> this.   
   > >>   
   > >> ChatGPT said:   
   > >>   
   > >> That warning usually shows up when you try to build a kernel module (for   
   > >> example with dkms or directly via make) and your current compiler binary   
   > >> is not exactly the same as the one used to build the running kernel.   
   > >>   
   > >> In your case, the versions are effectively identical:   
   > >>   
   > >> Kernel built with:   
   > >> x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0   
   > >>   
   > >> Your compiler:   
   > >> gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0   
   > >>   
   > >> The difference is just in the name of the binary   
   > >> (x86_64-linux-gnu-gcc-13 vs gcc-13), not the actual compiler version.   
   > >>   
   > >> ⚙️ What this means:   
   > >>   
   > >> It’s only a harmless warning. The kernel checks that the compiler string   
   > >> matches exactly, but the build is fine because the versions are identical.   
   > >>   
   > >> Ignore it, or ask Chat-GPT how to set an enviroment variable, CC   
   > >>   
   > >> --   
   > >> Adrian C   
   > >   
   > > Sadly when complete make -j4   
   > > after having edited /opt/media_build/backports/backports.txt   
   > > to comment out:   
   > >   
   > > [6.8.1023]   
   > > #  add v6.8-ccs.patch  }  recommended to avoid the problem below   
   > > add v6.8-spi.patch     }  but doesn't   
   > > add v6.8_remove.patch  }   
   > >   
   > > it ends like this:   
   > >   
   > >   CC [M]  /opt/media_build/v4l/ccs-limits.o   
   > > /opt/media_build/v4l/ccs-core.c: In function 'ccs_set_ctrl':   
   > > /opt/media_build/v4l/ccs-core.c:668:21: error: too many arguments to   
   function 'pm_runtime_get_if_active'   
   > >   668 |         pm_status = pm_runtime_get_if_active(&client->dev, true);   
   > >       |                     ^~~~~~~~~~~~~~~~~~~~~~~~   
   > > In file included from /opt/media_build/v4l/ccs-core.c:22:   
   > > ./include/linux/pm_runtime.h:75:12: note: declared here   
   > >    75 | extern int pm_runtime_get_if_active(struct device *dev);   
   > >       |            ^~~~~~~~~~~~~~~~~~~~~~~~   
   > >   CC [M]  /opt/media_build/v4l/ccs-data.o   
   > > make[4]: *** [scripts/Makefile.build:243: /opt/media_build/v4l/ccs-core.o]   
   Error 1   
   > > make[4]: *** Waiting for unfinished jobs....   
   > > make[3]: *** [/usr/src/linux-headers-6.8.0-51-generic/Makefile:1925:   
   /opt/media_build/v4l] Error 2   
   > > make[2]: *** [Makefile:240: __sub-make] Error 2   
   > > make[2]: Leaving directory '/usr/src/linux-headers-6.8.0-51-generic'   
   > > make[1]: *** [Makefile:53: default] Error 2   
   > > make[1]: Leaving directory '/opt/media_build/v4l'   
   > > make: *** [Makefile:26: all] Error 2   
   > > /opt/media_build$   
   > >   
   > > The reason I am using kernel version 6.8.0-51-generic is that was the   
   install kernel and alloewed me to use both screens. However I edited twom   
   lines in grub:   
   > >   
   > > #  GRUB_TIMEOUT_STYLE=hidden   
   > > GRUB_TIMEOUT=10   
   > >   
   > > to defer boot up until I had selected kernel version 6.8.0-51-generic and   
   now I only get one screen again!   
   > >   
   > > I am truly cheesed off.   
   > >   
   > > Alan   
   >   
   > Um, did you do a "make clean" in the build tree   
   > between each one of these adventures ? Or are you   
   > following the recipe and starting clean each time   
   > and making the modification and so on ?   
   >   
   > I think I may have done a "make clean" at some point, or   
   > something similar.   
   >   
   >    Paul   
   >   
      
   I have not only run make clean but also make distclean.   
   ChatGPT-5 has been gradually knocking down the reason for the errors.   
   It then tells me which library files to install and off we go again.   
   But each time we stop and repair, then we go on longer.   
   Right now make has been running for at least 15 minutes which is record   
   for this job. I'm keeping everything crossed.   
      
   Alan   
      
   --   
   Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8   
   AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)