From: nospam@needed.invalid   
      
   On Sun, 9/28/2025 7:37 AM, 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.   
   .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   
      
   Saw that during my build of your stuff, they are actually the same compiler.   
      
   Note that, when you install some of the cross-compiler packages, they have   
   long executable path names as well (similar to x86_64-linux-gnu-gcc-13), and   
   those could be soft links to the actual compiler file, or they could be scripts   
   of some sort which call the compiler (eventually). When the compiler was built,   
   perhaps the build machine, it did a path evaluation, running into one of the   
   many staged copies. Rather than the "plain" path entry gcc-13 (or just gcc -V   
   if they were clever). The package information indicates they are at the same   
   release level.   
   The kernel building machine, could actually be cross-compiling for a number   
   of platforms, such as ARM or RISC-V and x86_64 was "just one of the platforms   
   we build for" and treated no differently. They could have been in essence   
   "cross compiling for x86_64 while actually *on* x86_64" and that is why   
   your home build of a kernel (which is not staged for cross compiling)   
   resolves to a different GCC invocation location than the fancy-name   
   the kernel build happened to use.   
      
   Carry on :-)   
      
   Back to work.   
      
   You need some "symptoms", to tell me this is causing your actual build problem.   
      
   There can be warnings (not errors) during TBSDTV build, but as long   
   as it makes it to the end, then it is time to go onto the next steps.   
   These next steps, I did not test, as the steps after the build would be the   
   install.   
   Every step has its own risks.   
      
   When you installed "build-essential", it is a meta-package that puts a   
   basic build set in place. It may include GCC and PERL, you'd have to check   
   to see what the entire list is. As far as I know, build-essential is   
   enough to build a kernel, but it can build many other things as well.   
   The rust compiler (now a part of building the entire kernel, not your   
   package), may be built in place (not sure), it may not necessarily   
   come from a distro package.   
      
   I only did the build of your package, to basically prove I could finish   
   the compiling stage. And it did seem to hit the end OK. Once that one item   
   in the control file was commented out (and you commented you'd already   
   done that), it seemed to be clear sailing after that. Only resolving   
   the location of the "vmlinux" location so the build environment finds   
   it, remains to be done. In the real kernel build (I built the entire   
   6.8.0 kernel on my LM222 VM, compile was pretty slow), the vmlinux file   
   on there is around 400MB, whereas the real vmlinux file is a lot smaller, like   
   maybe 10MB or so and the one on the machine as the runtime seems   
   to be in /boot. I don't know what the intention of the TBSDTV build   
   is, in terms of which vmlinux it wants as reference materials.   
   As far as I know, the one in your /boot would be considered to be   
   a genkernel-derived one, so it should be good enough for install   
   on your own machine at least. I don't know what purpose would be   
   served, referencing the giant one in the 6.8.0 entire kernel build.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)