linux-kernel - Re: [PATCH 2/2] Makefile: "make kernelrelease" should show the correct full kernel version

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C6B88A5.4050305@inria.fr>
Date:	Wed, 18 Aug 2010 09:15:49 +0200
From:	Brice Goglin <Brice.Goglin@...ia.fr>
To:	Amerigo Wang <amwang@...hat.com>
CC:	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
	David Rientjes <rientjes@...gle.com>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH 2/2] Makefile: "make kernelrelease" should show the correct
 full kernel version

This patch (actually 01ab17887 in 2.6.36-rc1) reveals what looks like a
problem to me: make kernelrelease always regenerates
include/config/kernel.release even if it's already more recent than
include/config/auto.conf. Is this the expected behavior? Do we really
need include/config/kernel.release to depend on FORCE?

$ make kernelrelease -d
[...]
Considering target file `kernelrelease'.
 File `kernelrelease' does not exist.
  Considering target file `include/config/kernel.release'.
    Pruning file `include/config/auto.conf'.
    Considering target file `FORCE'.
     File `FORCE' does not exist.
     Finished prerequisites of target file `FORCE'.
    Must remake target `FORCE'.
    Successfully remade target file `FORCE'.
   Finished prerequisites of target file `include/config/kernel.release'.
   Prerequisite `include/config/auto.conf' is older than target `include/config/kernel.release'.
   Prerequisite `FORCE' of target `include/config/kernel.release' does not exist.
  Must remake target `include/config/kernel.release'.


Thanks,
Brice




Le 28/06/2010 05:01, Amerigo Wang a écrit :
> From: Amerigo Wang <amwang@...hat.com>
> Date: Mon, 28 Jun 2010 10:45:21 +0800
>
> After commit 85a256d8e0116c8f5ad276730830f5d4d473344d, 'make kernelrelease' doesn't
> show the correct full kernel version. This patch fixes it, 'make kernelrelease' will
> show the same version name with the one you finally get.
>
> Cc: David Rientjes <rientjes@...gle.com>
> Cc: Michal Marek <mmarek@...e.cz>
> Signed-off-by: Amerigo Wang <amwang@...hat.com>
> ---
>  Makefile |    5 ++---
>  1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 710f91c..2b517a1 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -414,7 +414,7 @@ endif
>  no-dot-config-targets := clean mrproper distclean \
>  			 cscope TAGS tags help %docs check% \
>  			 include/linux/version.h headers_% \
> -			 kernelrelease kernelversion
> +			 kernelversion
>  
>  config-targets := 0
>  mixed-targets  := 0
> @@ -1468,8 +1468,7 @@ checkstack:
>  	$(PERL) $(src)/scripts/checkstack.pl $(CHECKSTACK_ARCH)
>  
>  kernelrelease:
> -	$(if $(wildcard include/config/kernel.release), $(Q)echo $(KERNELRELEASE), \
> -	$(error kernelrelease not valid - run 'make prepare' to update it))
> +	@echo $(kernelrelease)
>  kernelversion:
>  	@echo $(KERNELVERSION)
>  
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/