linux-kernel - Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).

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]

Date:	Mon, 31 Dec 2007 11:10:21 -0500
From:	Dave Jones <davej@...hat.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Recursive variable `KBUILD_CFLAGS' references itself
	(eventually).

On Mon, Dec 31, 2007 at 02:16:19PM +0100, Sam Ravnborg wrote:

 > > Trying to do a 32bit build on a 64bit machine.
 > > I did..
 > >   make ARCH=i386 oldconfig
 > >   make ARCH=i386 arch/x86/
 > 
 > Walking through my mailbox I found this one.
 > I did not get similar reports and I cannot reproduce it.
 > Do you continue to see this or had it been fixed somehow?

Still happens for me with the latest tree from git.

$ make ARCH=i386 arch/x86/
  HOSTCC  scripts/kconfig/conf.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  CALL    scripts/checksyscalls.sh
/mnt/raid0/src/linux-2.6/arch/x86/Makefile_32:43: *** Recursive variable `KBUILD_CFLAGS' references itself (eventually).  Stop.
make: *** [arch/x86/] Error 2

 > The only way I can see it heppen is that you have lost
 > the initial assignmnet in top-level Makefile so
 > make see this as an '=' assinment and not a ':='
 > assignment.

$ git diff Makefile
$

(This tree is completely pristine, no changes at all)

	Dave

-- 
http://www.codemonkey.org.uk
--
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/