From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org
Subject: Re: Cross compiling using separate output directory problems
Date: Wed, 8 Oct 2003 18:06:01 +0200 [thread overview]
Message-ID: <20031008160601.GA11550@mars.ravnborg.org> (raw)
In-Reply-To: <16259.35252.163910.512212@wombat.chubb.wattle.id.au>
On Wed, Oct 08, 2003 at 01:51:16PM +1000, Peter Chubb wrote:
>
> Hi Sam,
> Thanks for doing the work to make comnpilation work with a separate
> output directory.
Thanks, but Kai Germaschewski did most of the infrastructure woark, I
just made the final stuff. He deserves credits more than I do.
> I found the following changes necessary to get it to work properly
> when crosscompiling for IA64. Otherwise include/asm-ia64 hasn't been
> created when setting up offsets.h.
>
> There's also a minor change to tell make where to find the
> toolchain-flags and check-gas scripts.
I'm glad to see people having interest in it, I have notice several
architectures catching up on it.
A few minor comments.
>
> -GAS_STATUS=$(shell arch/ia64/scripts/check-gas $(CC) $(OBJDUMP))
> +GAS_STATUS=$(shell $(src)/arch/ia64/scripts/check-gas $(CC) $(OBJDUMP))
I prefer the use of $(srctree), which is pointing to the root
of the kernel src tree. src works here because the file is included
from the top-level Makefile.
> -CPPFLAGS += $(shell arch/ia64/scripts/toolchain-flags $(CC) $(OBJDUMP))
> +CPPFLAGS += $(shell $(src)/arch/ia64/scripts/toolchain-flags $(CC) $(OBJDUMP))
Same goes here.
>
> -CLEAN_FILES += include/asm-ia64/.offsets.h.stamp include/asm-ia64/offsets.h vmlinux.gz bootloader
> +CLEAN_FILES += include/asm-$(ARCH)/.offsets.h.stamp include/asm-$(ARCH)/offsets.h vmlinux.gz bootloader
s#$(ARCH)#ia64#g is unrelated, but OK.
I assume you will push this to David Mosberger.
Sam
prev parent reply other threads:[~2003-10-08 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 3:51 Peter Chubb
2003-10-08 16:06 ` 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=20031008160601.GA11550@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.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®