From: Vincent Daanen <vincent.daanen@orthotaxy.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: defconfig file (or fragment files) not used
Date: Fri, 30 Mar 2018 13:08:43 +0000 [thread overview]
Message-ID: <VI1P192MB0143A7A3AA8AB0E0433F0E738DA10@VI1P192MB0143.EURP192.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4d479834-e8a6-0f65-e34f-2cbd271192bd@windriver.com>
Hi
> On 03/29/18 16:12 PM, Bruce Ashfield wrote:
> [cut]
> Do you have all of the CAN* Kconfig dependencies in your defconfig ?
No only the ones I need
> If you don't, the kernel config subsystem will turn them off.
>
> Also note that a 'defconfig' translates to a merge config run (yes, even with just a defconfig) of 'allnoconfig', so that can also be turning off dependencies if they were only valid via their default and were not explicitly specified.
>
> You can set KCONFIG_MODE="alldefconfig" in a linux-yocto bbappend to change what mode merge-config uses.
I tried this but got the same result ☹!
Do you think I have to set all the "CAN*" dependencies?
Vincent
next prev parent reply other threads:[~2018-03-30 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 16:27 defconfig file (or fragment files) not used Vincent Daanen
2018-03-29 0:13 ` Khem Raj
2018-03-29 6:00 ` Vincent Daanen
2018-03-29 8:25 ` Khem Raj
2018-03-29 9:45 ` Prakash Ks
2018-03-29 10:42 ` Vincent Daanen
2018-03-29 11:06 ` Prakash Ks
2018-03-29 14:12 ` Bruce Ashfield
2018-03-30 13:08 ` Vincent Daanen [this message]
2018-03-30 15:18 ` Bruce Ashfield
2018-04-04 9:58 ` Vincent Daanen
2018-04-04 12:22 ` 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=VI1P192MB0143A7A3AA8AB0E0433F0E738DA10@VI1P192MB0143.EURP192.PROD.OUTLOOK.COM \
--to=vincent.daanen@orthotaxy.com \
--cc=bruce.ashfield@windriver.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.