All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Andreas Fenkart <afenkart@gmail.com>, <yocto@yoctoproject.org>
Subject: Re: Problems using "In-Tree" defconfig File
Date: Fri, 19 Jun 2015 12:19:52 -0400	[thread overview]
Message-ID: <55844128.9030507@windriver.com> (raw)
In-Reply-To: <CALtMJECkfxQz+tabTRVL9JcZUNgO+Oho_JcssbCWkZdEEmCsvg@mail.gmail.com>

On 2015-06-19 03:28 AM, Andreas Fenkart wrote:
> I want to use a defconfig, that is provided by the linux git
> repository, hence this seems to fit my need:
>
> http://www.yoctoproject.org/docs/1.8/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
> KBUILD_DEFCONFIG_KMACHINE ?= defconfig_file
>
> Anybody used that feature recently? I couldn't get it to work, :-(

Works here.

>
> The build fails in kernel_config target, in merge_config.sh. It fails
> to merge kernel config fragments. Probably because I don't have any.
>
> [INFO] collecting configs in .meta/meta-series
> ARCH=arm O=<path>/linux-dss11e-standard-build merge_config.sh -d
> mv: cannot stat '<path>/linux-dss11e-standard-build/.tmp.config*': No
> such file or directory

This actually means something else, like a misconfigured BSP.

>
> Grep'ing for KBUILD_DEFCONFIG in kernel-tools only get_defconfig seems
> to use  that variable
>
> $ get_defconfig arm dss20_defconfig
> linux/arch/arm/configs/dss20_defconfig      ...so that works fine
>
> I took that snipped from check_defconfig functoin, here:
> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-tools/tree/tools/createme#n201
>
> but that function is not called anywhere in script createme. After all
> that script only creates the meta folder but has nothing to do with
> kernel configuration. Seems to be a dead end. Probably get_defconfig
> call should be added to configme script

In this case no. What release are you using ? And what does your kernel
recipe look like ?

do_kernel_metadata is responsible for yanking that defconfig out of the
tree and feeding it into the build just like a 'defconfig' passed via
the SRC_URI.

Bruce

>
> Anybody had the same problem, is there a patch. Or did I misconfigure something?
>
> kind regards,
> Andi
>
>
> Here my recipe:
> ---------------------------------------------------------------------------------------------------------------
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> SRCBRANCH = "dSS"
> SRCREV="82d97d74bb072fe24be10b46d0782d3735130199"
> SRC_URI =
> "git://git.digitalstrom.org/bsp/linux.git;protocol=https;branch=${SRCBRANCH}"
>
> LINUX_VERSION = "4.1"
> LINUX_VERSION_EXTENSION = ""
> KBUILD_DEFCONFIG_dss11e = "dss20_defconfig"
>
> PR = "r1"
> PV = "${LINUX_VERSION}+git${SRCPV}"
>
> COMPATIBLE_MACHINE = "(dss11e)"
>



      reply	other threads:[~2015-06-19 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  7:28 Problems using "In-Tree" defconfig File Andreas Fenkart
2015-06-19 16:19 ` Bruce Ashfield [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=55844128.9030507@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=afenkart@gmail.com \
    --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.