<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>In Documentation/kbuild/makefiles.txt, you can see:<br><br></div>...<br>1365 VERSION, PATCHLEVEL, SUBLEVEL, EXTRAVERSION<br>1366 <br>1367 These variables define the current kernel version. A few arch<br>1368 Makefiles actually use these values directly; they should use<br>1369 $(KERNELRELEASE) instead.<br>1370 <br>1371 $(VERSION), $(PATCHLEVEL), and $(SUBLEVEL) define the basic<br>1372 three-part version number, such as "2", "4", and "0". These three<br>1373 values are always numeric.<br>1374 <br>1375 $(EXTRAVERSION) defines an even tinier sublevel for pre-patches<br>1376 or additional patches. It is usually some non-numeric string<br>1377 such as "-pre4", and is often blank.<br>1378 <br>1379 KERNELRELEASE<br>1380 <br>1381 $(KERNELRELEASE) is a single string such as "2.4.0-pre4", suitable<br>1382 for constructing installation directory names or showing in<br>1383 version strings. Some arch Makefiles use it for this purpose.<br>1384 <br>1385 ARCH<br>1386 <br>1387 This variable defines the target architecture, such as "i386",<br>1388 "arm", or "sparc". Some kbuild Makefiles test $(ARCH) to<br>1389 determine which files to compile.<br>1390 <br>1391 By default, the top Makefile sets $(ARCH) to be the same as the<br>1392 host system architecture. For a cross build, a user may<br>1393 override the value of $(ARCH) on the command line:<br>1394 <br>1395 make ARCH=m68k ..<br>...<br><br><div>--<br><div>Regards,<br>shhuiw<br></div></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2014-07-10 11:28:39, "Safarin" <safarin87@gmail.com> wrote:
>Hi Guys,
>
>This question might be very easy for all of you. But seem this is
>kernelnewbies mailing list. I need to ask this question.
>
>I in the middle of learning to build custom kernel and my question is
>how to have custom name for kernel version.
>
>$ uname -r
>
>I can see custom kernel print message.
>
>>From what I read, we can change inside .config
>CONFIG_LOCALVERSION="-ARCH"
>will produce the kernel release naming something like this.
>3.16.0-rc3-ARCH
>
>But somehow, when I try to install the modules
>
>$make modules_install
>
>I can see makefile create folder inside the lib/modules with naming
>3.16.0-rc3-ARCH-00570-g110e430
>
>110e430 is actually commit id and I check that naming is generated by
>#define UTS_RELEASE "3.16.0-rc3-ARCH-00570-g110e430" in the
>"include/generated/utsrelease.h" header which will
>overwrite "include/config/kernel.release".
>
>Back to the question, what is the practical way to naming the kernel
>release for custom kernel? with additional question for understanding
>more from where that utsrelease came from?
>
>Thanks,
>
>Regards,
>Safarin
>
>_______________________________________________
>Kernelnewbies mailing list
>Kernelnewbies@kernelnewbies.org
>http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
</pre></div>