From: Mohan Kumar M <mohan@in.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Integrating relocatable kernel build with kernel build
Date: Thu, 10 Jul 2008 19:40:22 +0530 [thread overview]
Message-ID: <4876184E.7040705@in.ibm.com> (raw)
In-Reply-To: <20080709202740.GA2655@uranus.ravnborg.org>
Hi Sam,
Thank you for the reply.
Sam Ravnborg wrote:
> Hi Mohan.
>
>
> Add the relevant target to the all: rule in arch/powerpc/Makefile
>
> # Default to zImage, override when needed
> all: zImage
I added vmlinux.reloc here and now by default vmlinux.reloc is also built.
>
> And include support for the target in same file.
>
>
>> 2. During build process, build is not able to build the
>> vmlinux.reloc.lds linker script from the vmlinux.reloc.lds.S source file.
>
> If you just add:
> extra-y += vmlinux.reloc.lds
After including the above entry, make builds the linker script.
>
> then it should happen automatically.
> ee how all archs does it in arch/$ARCH/kernel/Makefile for vmlinx.lds
>
> I did not look at it this time - lacking time.
> But tr to provide a single unified diff next time - that i
> at least remotely readable.
>
>> Another feature I am looking is to generate the "relocatable vmlinux"
>> image in the top directory of kernel source and the intermediate vmlinux
>> file either in arch/powerpc/kernel or arch/powerpc/boot.
> We no longer build arch specific targets in the top-level directory
> of the kernel src. We print out where to locate the build file.
>
Still need to build the final "relocatable vmlinux" image in the top
level directory of kernel source (either as vmlinux or vmlinux.reloc).
Once again thank you.
Regards,
Mohan.
next prev parent reply other threads:[~2008-07-10 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 18:31 Integrating relocatable kernel build with kernel build Mohan Kumar M
2008-07-09 20:27 ` Sam Ravnborg
2008-07-10 14:10 ` Mohan Kumar M [this message]
2008-07-10 19:44 ` 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=4876184E.7040705@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=linux-kbuild@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