2023-03-09 21:15:42

by Guilherme G. Piccoli

[permalink] [raw]
Subject: About the .scmversion removal (commit f6e09b07cc12)

Hi Masahiro / all, I was rebuilding the kernel today, just adding some
debug statements, when I noticed a lot of stuff got built again. I was
using ".scmversion" to prevent UTS version changes, so only affected
files got indeed rebuilt.

After commit f6e09b07cc12 ("kbuild: do not put .scmversion into the
source tarball"), seems this file is automatically deleted and I'm not
sure how should I proceed to continue with the same behavior.

Apologies if this is a silly question, any advice is much appreciated!
Also, I've CCed all the emails from [0], so apologies if anybody looped
here shouldn't be CCed.

Cheers,


Guilherme


[0]
https://lore.kernel.org/lkml/[email protected]/


2023-03-10 00:52:40

by Masahiro Yamada

[permalink] [raw]
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)

On Fri, Mar 10, 2023 at 6:15 AM Guilherme G. Piccoli
<[email protected]> wrote:
>
> Hi Masahiro / all, I was rebuilding the kernel today, just adding some
> debug statements, when I noticed a lot of stuff got built again. I was
> using ".scmversion" to prevent UTS version changes, so only affected
> files got indeed rebuilt.
>
> After commit f6e09b07cc12 ("kbuild: do not put .scmversion into the
> source tarball"), seems this file is automatically deleted and I'm not
> sure how should I proceed to continue with the same behavior.
>
> Apologies if this is a silly question, any advice is much appreciated!
> Also, I've CCed all the emails from [0], so apologies if anybody looped
> here shouldn't be CCed.


Not a silly question, but .scmversion was intended for source
package creation (deb, rpm) in my understanding.

If you want to use a fixed string for the UTS version,
please pass KERNELRELEASE=<some-string> to the build command line.






--
Best Regards
Masahiro Yamada

2023-03-10 15:47:48

by Guilherme G. Piccoli

[permalink] [raw]
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)

On 09/03/2023 21:51, Masahiro Yamada wrote:
> [...]
> Not a silly question, but .scmversion was intended for source
> package creation (deb, rpm) in my understanding.
>
> If you want to use a fixed string for the UTS version,
> please pass KERNELRELEASE=<some-string> to the build command line.
>

Thanks! It seems..it didn't work for me, probably I'm doing something wrong.

KERNELRELEASE="6.3.0-rc1-gpiccoli" make all -j128
Does it make sense for you? It gets me:


$ file arch/x86/boot/bzImage

arch/x86/boot/bzImage: Linux kernel x86 boot executable bzImage, version
6.3.0-rc1-gpiccoli-00003-gb6224c91dbaa (gpiccoli@buildbox2) [...]


Thanks in advance,


Guilherme

2023-03-12 08:16:14

by Masahiro Yamada

[permalink] [raw]
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)

On Sat, Mar 11, 2023 at 12:37 AM Guilherme G. Piccoli
<[email protected]> wrote:
>
> On 09/03/2023 21:51, Masahiro Yamada wrote:
> > [...]
> > Not a silly question, but .scmversion was intended for source
> > package creation (deb, rpm) in my understanding.
> >
> > If you want to use a fixed string for the UTS version,
> > please pass KERNELRELEASE=<some-string> to the build command line.
> >
>
> Thanks! It seems..it didn't work for me, probably I'm doing something wrong.
>
> KERNELRELEASE="6.3.0-rc1-gpiccoli" make all -j128

Try this:

make all -j128 KERNELRELEASE="6.3.0-rc1-gpiccoli"






--
Best Regards
Masahiro Yamada

2023-03-12 16:38:35

by Guilherme G. Piccoli

[permalink] [raw]
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)

On 12/03/2023 05:15, Masahiro Yamada wrote:
> [...]
> Try this:
>
> make all -j128 KERNELRELEASE="6.3.0-rc1-gpiccoli"
>

Worked like a charm! Thanks a lot for the help =)
Cheers,


Guilherme