<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>6611</bug_id>
          
          <creation_ts>2014-08-05 19:55:41 +0000</creation_ts>
          <short_desc>linux-yocto based recipes require a config (won&apos;t use Linux defconfig)</short_desc>
          <delta_ts>2015-06-17 19:09:36 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Kernel</product>
          <component>kernel-tooling</component>
          <version>1.7</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>17 June 2015: Documentation revisions made.  Needs review.</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.9 M3</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Darren Hart">dvhart</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>bruce.ashfield</cc>
    
    <cc>srifenbark</cc>
    
    <cc>yp.kernel.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>44968</commentid>
    <comment_count>0</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2014-08-05 19:55:41 +0000</bug_when>
    <thetext>When attempting to write a linux-yocto-custom based recipe for 3.16 for x86_64, I found if I didn&apos;t specify a defconfig, the build would complain:

Log data follows:                                                                   | DEBUG: Executing shell function do_kernel_configme
| [INFO] doing kernel configme
| [INFO] Configuring target/machine combo: &quot;standard/intel-corei7-64&quot;
| [INFO] collecting configs in ./.meta/meta-series
| cat: .meta/cfg/standard/intel-corei7-64/config_frag.txt: No such file or directory
| cat: .meta/cfg/standard/intel-corei7-64/config_frag.txt: No such file or directory
| mv: cannot stat &apos;/build/yocto/master/intel-corei7-64_20140718213113/build/tmp/work/intel_corei7_64-eywa-linux/linux-eywa/3.16+gitAUTOINC+f845b06934-r0/linux-intel_corei7_64-standard-build/.tmp.config*&apos;: No such file or directory
| creation of pre-processed config data failed
| config of &quot;standard/intel-corei7-64&quot; failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at /build/yocto/master/intel-corei7-64_20140718213113/build/tmp/work/intel_corei7_64-eywa-linux/linux-eywa/3.16+gitAUTOINC+f845b06934-r0/temp/log.do_kernel_configme.13711)

However, if I ran the following:

$ make defconfig

in a linux source directory and copied the resulting .config to the files dir as defconfig and added it to the SRC_URI, the build would complete.

I would expect the tools to default to &quot;make defconfig&quot; in the absence of any other configuration data.

Bruce - what are your thoughts. This is either a bug against the kern tools, or a bug against linux-yocto-custom and the kernel development manual, depending on what we agree the expectations to be.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>44988</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2014-08-07 03:12:20 +0000</bug_when>
    <thetext>It&apos;s a documentation issue, since you must specify something
for a configuration .. i.e. a defconfig or fragments.

That being said, the error message for this is really nasty,
so I can take the bug and use it to improve the message, which
is the documentation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>44989</commentid>
    <comment_count>2</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2014-08-07 05:37:55 +0000</bug_when>
    <thetext>We&apos;ll need to update the kernel-dev manual as well. Adding Scott.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>49476</commentid>
    <comment_count>3</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2015-03-16 19:26:02 +0000</bug_when>
    <thetext>I&apos;ve emailed Scott on this. Looking for the right place to document it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>49498</commentid>
    <comment_count>4</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2015-03-17 17:06:15 +0000</bug_when>
    <thetext>Hi, 

I have a section in the YP Linux Kernel Development Manual that is titled &quot;Modifying an Existing Recipe&quot; (http://www.yoctoproject.org/docs/kernel-dev/kernel-dev.html#modifying-an-existing-recipe).  This section has some sub-sections.  Originally, I thought that we could address this with a note in the section that talks about changing the configuration.  Bruce indicates, though, that it is not quite the same.  So, if this involves only &quot;using&quot; custom Linux-yocto kernels and does not involve creating them, which is what I thought this existing section would cover, then do we want a brand new section called &quot;Using Custom Linux-Yocto Kernel Recipes&quot;?

Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>51258</commentid>
    <comment_count>5</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2015-05-26 12:56:07 +0000</bug_when>
    <thetext>Hi, 

I found what I think would be an appropriate section to note this requirement when using the yocto-linux-custom.bb recipe.  I have added a step to the list and noted some more information in the description of SRC_URI.  Please look this over and let me know if this will meet the documentation requirement of this bug.

http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-your-own-sources

See step 3 and the description for SRC_URI in step 4.

Thanks, 
Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>51712</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2015-06-16 04:02:05 +0000</bug_when>
    <thetext>(In reply to comment #5)
&gt; Hi, 
&gt; 
&gt; I found what I think would be an appropriate section to note this
&gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; step to the list and noted some more information in the description of
&gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; documentation requirement of this bug.
&gt; 
&gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; your-own-sources
&gt; 
&gt; See step 3 and the description for SRC_URI in step 4.
&gt; 
&gt; Thanks, 
&gt; Scott

(In reply to comment #5)
&gt; Hi, 
&gt; 
&gt; I found what I think would be an appropriate section to note this
&gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; step to the list and noted some more information in the description of
&gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; documentation requirement of this bug.
&gt; 
&gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; your-own-sources
&gt; 
&gt; See step 3 and the description for SRC_URI in step 4.

We should add more text around step #3. When you do a &apos;make defconfig&apos;,
you are getting the kernel defined default configuration for your
architecture, but there is no guarantee that it is valid for your
use case, or will even boot your board. This is particularly true in
non-x86 architectures. To use non-x86 defconfigs, you need to be a 
bit more specific and fine one that matches your board. 

i.e. for arm, you look in &quot;arch/arm/configs&quot; and fine the one that
is the best starting point for your board.

Alternatively, your board vendor may supply a baseline .config, that
you copy into place and call &apos;defconfig&apos;.

The SRC_URI changes look fine.


&gt; 
&gt; Thanks, 
&gt; Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>51760</commentid>
    <comment_count>7</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2015-06-17 12:52:42 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; (In reply to comment #5)
&gt; &gt; Hi, 
&gt; &gt; 
&gt; &gt; I found what I think would be an appropriate section to note this
&gt; &gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; &gt; step to the list and noted some more information in the description of
&gt; &gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; &gt; documentation requirement of this bug.
&gt; &gt; 
&gt; &gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; &gt; your-own-sources
&gt; &gt; 
&gt; &gt; See step 3 and the description for SRC_URI in step 4.
&gt; &gt; 
&gt; &gt; Thanks, 
&gt; &gt; Scott
&gt; 
&gt; (In reply to comment #5)
&gt; &gt; Hi, 
&gt; &gt; 
&gt; &gt; I found what I think would be an appropriate section to note this
&gt; &gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; &gt; step to the list and noted some more information in the description of
&gt; &gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; &gt; documentation requirement of this bug.
&gt; &gt; 
&gt; &gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; &gt; your-own-sources
&gt; &gt; 
&gt; &gt; See step 3 and the description for SRC_URI in step 4.
&gt; 
&gt; We should add more text around step #3. When you do a &apos;make defconfig&apos;,
&gt; you are getting the kernel defined default configuration for your
&gt; architecture, but there is no guarantee that it is valid for your
&gt; use case, or will even boot your board. This is particularly true in
&gt; non-x86 architectures. To use non-x86 defconfigs, you need to be a 
&gt; bit more specific and fine one that matches your board. 
&gt; 
&gt; i.e. for arm, you look in &quot;arch/arm/configs&quot; and fine the one that
&gt; is the best starting point for your board.
&gt; 
&gt; Alternatively, your board vendor may supply a baseline .config, that
&gt; you copy into place and call &apos;defconfig&apos;.

Bruce, Check out http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-your-own-sources section and Step 3 now.  I have your suggestions in.  Let me know if this works. 

&gt; 
&gt; The SRC_URI changes look fine.
&gt; 
&gt; 
&gt; &gt; 
&gt; &gt; Thanks, 
&gt; &gt; Scott</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>51765</commentid>
    <comment_count>8</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2015-06-17 14:40:03 +0000</bug_when>
    <thetext>(In reply to comment #7)
&gt; (In reply to comment #6)
&gt; &gt; (In reply to comment #5)
&gt; &gt; &gt; Hi, 
&gt; &gt; &gt; 
&gt; &gt; &gt; I found what I think would be an appropriate section to note this
&gt; &gt; &gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; &gt; &gt; step to the list and noted some more information in the description of
&gt; &gt; &gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; &gt; &gt; documentation requirement of this bug.
&gt; &gt; &gt; 
&gt; &gt; &gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; &gt; &gt; your-own-sources
&gt; &gt; &gt; 
&gt; &gt; &gt; See step 3 and the description for SRC_URI in step 4.
&gt; &gt; &gt; 
&gt; &gt; &gt; Thanks, 
&gt; &gt; &gt; Scott
&gt; &gt; 
&gt; &gt; (In reply to comment #5)
&gt; &gt; &gt; Hi, 
&gt; &gt; &gt; 
&gt; &gt; &gt; I found what I think would be an appropriate section to note this
&gt; &gt; &gt; requirement when using the yocto-linux-custom.bb recipe.  I have added a
&gt; &gt; &gt; step to the list and noted some more information in the description of
&gt; &gt; &gt; SRC_URI.  Please look this over and let me know if this will meet the
&gt; &gt; &gt; documentation requirement of this bug.
&gt; &gt; &gt; 
&gt; &gt; &gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; &gt; &gt; your-own-sources
&gt; &gt; &gt; 
&gt; &gt; &gt; See step 3 and the description for SRC_URI in step 4.
&gt; &gt; 
&gt; &gt; We should add more text around step #3. When you do a &apos;make defconfig&apos;,
&gt; &gt; you are getting the kernel defined default configuration for your
&gt; &gt; architecture, but there is no guarantee that it is valid for your
&gt; &gt; use case, or will even boot your board. This is particularly true in
&gt; &gt; non-x86 architectures. To use non-x86 defconfigs, you need to be a 
&gt; &gt; bit more specific and fine one that matches your board. 
&gt; &gt; 
&gt; &gt; i.e. for arm, you look in &quot;arch/arm/configs&quot; and fine the one that
&gt; &gt; is the best starting point for your board.
&gt; &gt; 
&gt; &gt; Alternatively, your board vendor may supply a baseline .config, that
&gt; &gt; you copy into place and call &apos;defconfig&apos;.
&gt; 
&gt; Bruce, Check out
&gt; http://www.yoctoproject.org/docs/1.9/kernel-dev/kernel-dev.html#working-with-
&gt; your-own-sources section and Step 3 now.  I have your suggestions in.  Let
&gt; me know if this works. 

This looks good to me.

Bruce

&gt; 
&gt; &gt; 
&gt; &gt; The SRC_URI changes look fine.
&gt; &gt; 
&gt; &gt; 
&gt; &gt; &gt; 
&gt; &gt; &gt; Thanks, 
&gt; &gt; &gt; Scott</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>