| 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
| ||
|
Message-ID: <12875.1174542222@kao2.melbourne.sgi.com> Date: Thu, 22 Mar 2007 16:43:42 +1100 From: Keith Owens <kaos@....com.au> To: Dave Jones <davej@...hat.com> cc: Linux Kernel <linux-kernel@...r.kernel.org>, sam@...nborg.org Subject: Re: $CHECK can't be overridden Dave Jones (on Thu, 22 Mar 2007 01:37:14 -0400) wrote: >On Thu, Mar 22, 2007 at 04:26:39PM +1100, Keith Owens wrote: > > Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote: > > >make help implies that supplying $CHECK on the command line > > >should override sparse as the checker used when building with C=1 > > >Yet, this doesn't seem to be the case. > > > > > >This would be useful for cases where for eg, sparse isn't in > > >the $PATH, allowing an explicit path to the executable to be > > >passed in automated build environments. > > > > Works for me. > > > > # make C=1 CHECK=foo > >Ah, my bad. I was thinking it was an environment var rather >than a makefile var. I was using 'CHECK=foo make bzImage C=1' The default for 'make' is that environment variables do _not_ override variables defined in the Makefiles. You can change that behaviour with the -e flag, 'CHECK=foo make -e bzImage C=1' should work. 'info make' recommends against using -e, changing environments can lead to unexpected side effects. - 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/
Powered by blists - more mailing lists