Why /boot/vmlinuz differs from what i get after recompling the kernel source

Yes, of course – my mistake for not being clear enough with respect to the “Open Build Service (OBS)” versus the «public instance of» “openSUSE Build Service” jungle …

  • And, you’re correct – the openSUSE Kernel is “based on
    ” the SLE Kernel …

[HR][/HR]Incestuous relationships are fun – especially when, the bills are being paid …

I just discovered an interesting on one of those »Stackexchange«/»Superuser« forums:
https://superuser.com/questions/639351/does-recompiling-a-program-produce-a-bit-for-bit-identical-binary (»Does recompiling a program produce a bit-for-bit identical binary?«)
Much interesting info with links to more info, especially gcc-specific features like …

       -frandom-seed=string
           This option provides a seed that GCC uses when it would otherwise
           use random numbers.  It is used to generate certain symbol names
           that have to be different in every compiled file.  It is also used
           to place unique stamps in coverage data files and the object files
           that produce them.  You can use the -frandom-seed option to produce
           reproducibly identical object files.
           The string should be different for every file you compile.

It’s another proverbial can of worms that just managed to remind me once more why I’ve chosen all that »blinkenlights« stuff as a hobby fourty years ago (and later as a profession).
Cheers!