From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Dave Jones <davej@redhat.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).
Date: Thu, 24 Jan 2008 22:34:06 +0100 [thread overview]
Message-ID: <20080124213406.GD3944@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801242231040.12676@fbirervta.pbzchgretzou.qr>
On Thu, Jan 24, 2008 at 10:31:18PM +0100, Jan Engelhardt wrote:
>
> On Jan 24 2008 22:27, 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/
> >
> >There is no easy fx for this one.
> >You try to build one of the non-standard directories and it just
> >fails because arch/x86/Makefile is not a regular Kbuild file.
> >
> >Try with any other directory (almost any other) and it works.
> >Considered unfortunate but not a bug - so I will not try to fix it.
>
> So, how are we going to build only arch/x86/ right now with kbuild?
It is not poissible.
You can do:
make arch/x86/kernel/
make arch/x86/lib/
make arch/x86/mm/
But there is no easy way to build them in one go.
Sam
prev parent reply other threads:[~2008-01-24 21:34 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
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 [this message]
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=20080124213406.GD3944@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@redhat.com \
--cc=jengelh@computergmbh.de \
--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