From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Michael Stickel <michael@cubic.org>
Cc: yocto@yoctoproject.org
Subject: Re: Problem building the linux kernel outside source directory for mips
Date: Sun, 2 Jun 2013 16:23:55 -0400 [thread overview]
Message-ID: <51ABA9DB.2030204@windriver.com> (raw)
In-Reply-To: <51AB4815.6040006@cubic.org>
On 13-06-02 09:26 AM, Michael Stickel wrote:
> Hi,
>
> I am new to yocto, so I don't know if this is the right list.
This will work, we also have the linux-yocto@yoctoproject.org kernel
mailing list.
>
> I tried to build a kernel for the MTX-1 platform that uses an AU1500
> which is a MIPS32 based SoC.
> After some work I got the standard kernel (3.8.4) used in poky 9 to work.
> But I encountered some problems:
>
> In poky-dylan-9.0.0/meta/recipes-kernel/linux/linux-yocto.inc the
> builddir is set to
> "${WORKDIR}/linux-${MACHINE}-${LINUX_KERNEL_TYPE}-build", but
> KERNEL_EXTRA_ARGS does not contain O="${B}". How is the the out of
> source build of the kernel meant to work?
Can you elaborate on this ? Are you actually seeing a problem, or
just wondering about the glue ? If it's the glue, kernel-yocto.bbclass
sets:
KBUILD_OUTPUT = "${B}"
For the desired source/binary split.
>
> The task do_kernel_configme trashed my kernel config. This may be
> because defconfig is copied to ${B}/.config and do_kernel_configme is
> executed in ${S} and does not find .config.
Same question as above. This is basic functionality and kernel_configme
is aware of the source/binary split, and has been doing this since
yocto 0.9.
Can you define "trashed" ?
>
> Is the intended behavior of the out of source build for the kernel
> documented.
Everything should be in the kernel-dev manual and the other yocto
project documentation. There's not that much to document, since the
functionality has been unchanged for quite some time and works behind
the scenes for a linux-yocto* based build.
Cheers,
Bruce
>
> BTW: The kernel works and boots the core-image-minimal with usb USB
> Storage as rootfs.
>
> Best regards
> Michael
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2013-06-02 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 13:26 Problem building the linux kernel outside source directory for mips Michael Stickel
2013-06-02 20:23 ` Bruce Ashfield [this message]
2013-06-03 18:54 ` Michael Stickel
2013-06-03 19:29 ` Bruce Ashfield
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=51ABA9DB.2030204@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=michael@cubic.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.