From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Can't cross compile IA32 kernels using separate build directory
Date: Wed, 4 Aug 2004 23:05:39 +0200 [thread overview]
Message-ID: <20040804210538.GA7275@mars.ravnborg.org> (raw)
In-Reply-To: <E1BrpeA-0002QH-00@berry.gelato.unsw.EDU.AU>
On Tue, Aug 03, 2004 at 01:07:26PM +1000, Peter Chubb wrote:
>
> Hi Sam,
> Trying to cross compile a kernel for IA32, on a system without an asm/boot.h
> fails (e.g., IA64)
>
> Here's a patch to add in -Iinclude2 when building tools/build.o so that
> asm/boot.h is picked up from the right place.
I have boot.h in /usr/include/ thats why I did not see it. Running i386 as
you already guessed.
Knowledge of include2 should be restricted to the core kbuild files though,
so I will se if I can come up with something smarter.
That would require splitting CPPFLAGS in two parts and we already have
enough variables...
Sam
>
> Index: linux-2.6-wip/arch/i386/boot/Makefile
> ===================================================================
> --- linux-2.6-wip.orig/arch/i386/boot/Makefile 2004-08-03 12:58:02.287223257 +1000
> +++ linux-2.6-wip/arch/i386/boot/Makefile 2004-08-03 12:59:34.661245563 +1000
> @@ -31,7 +31,7 @@
>
> host-progs := tools/build
>
> -HOSTCFLAGS_build.o := -Iinclude
> +HOSTCFLAGS_build.o := -Iinclude -Iinclude2
>
> # ---------------------------------------------------------------------------
>
prev parent reply other threads:[~2004-08-04 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 3:07 Peter Chubb
2004-08-04 21:05 ` 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=20040804210538.GA7275@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/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
all inboxes | Powered by JetHome®