public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Jones <davej@redhat.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).
Date: Mon, 31 Dec 2007 14:16:19 +0100	[thread overview]
Message-ID: <20071231131619.GE21871@uranus.ravnborg.org> (raw)
In-Reply-To: <20071120001445.GA9243@redhat.com>

On Mon, Nov 19, 2007 at 07:14:45PM -0500, Dave Jones wrote:
> Trying to do a 32bit build on a 64bit machine.
> I did..
>   make ARCH=i386 oldconfig
>   make ARCH=i386 arch/x86/
> 
> and got..
> 
> scripts/kconfig/conf -s arch/x86/Kconfig
>   CHK     include/linux/version.h
>   UPD     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   UPD     include/linux/utsrelease.h
>   SYMLINK include/asm -> include/asm-x86
>   HOSTCC  scripts/kallsyms
>   HOSTCC  scripts/conmakehash
>   CC      scripts/mod/empty.o
>   HOSTCC  scripts/mod/mk_elfconfig
>   HOSTCC  scripts/bin2c
>   MKELF   scripts/mod/elfconfig.h
>   HOSTCC  scripts/mod/file2alias.o
>   HOSTCC  scripts/mod/modpost.o
>   HOSTCC  scripts/mod/sumversion.o
>   HOSTLD  scripts/mod/modpost
>   CC      arch/x86/kernel/asm-offsets.s
>   GEN     include/asm-x86/asm-offsets.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

Hi Dave.

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?
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.
The first may not reference itself.

	Sam

  reply	other threads:[~2007-12-31 13:16 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 [this message]
2007-12-31 16:10   ` Dave Jones
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=20071231131619.GE21871@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.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