From: Dave Jones <davej@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).
Date: Mon, 31 Dec 2007 11:10:21 -0500 [thread overview]
Message-ID: <20071231161021.GC27655@redhat.com> (raw)
In-Reply-To: <20071231131619.GE21871@uranus.ravnborg.org>
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
next prev parent reply other threads:[~2007-12-31 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 0:14 Recursive variable `KBUILD_CFLAGS' references itself (eventually) Dave Jones
2007-12-31 13:16 ` Sam Ravnborg
2007-12-31 16:10 ` Dave Jones [this message]
2008-01-01 0:49 ` Sam Ravnborg
2008-01-24 21:27 ` Sam Ravnborg
2008-01-24 21:31 ` Jan Engelhardt
2008-01-24 21:34 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071231161021.GC27655@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox