All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <samoht.yrag@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Can't select my own Kernel source
Date: Thu, 07 Aug 2014 07:44:34 -0600	[thread overview]
Message-ID: <53E382C2.7030304@gmail.com> (raw)
In-Reply-To: <1cc2cefed7bf40e5855eb488784508b0@BLUPR03MB565.namprd03.prod.outlook.com>

On 2014-08-07 07:38, filip.ghimpeteanu@freescale.com wrote:
> Yes it is available. Also when building it shows on the prompt that my recipe
> is being baked.
>
> What do you mean by checking local.conf and machine.conf?
> I placed the <PREFERRED_PROVIDER_virtual/kernel = "linux-yocto_myproj"> in local.conf.

I think this should be
   PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-myproj"
there's a difference between "-" and "_".  Also, you could add
   PREFERRED_VERSION_linux-yocto-myproj = "3.10%"

> A snapshot of the build log:
> -------------------------------------------------------------------------------------------------------
>
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_kernel_link_vmlinux: Started
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_compile_kernelmodules: Started
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_uboot_mkimage: Started
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_uboot_mkimage: Succeeded
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_kernel_link_vmlinux: Succeeded
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_compile_kernelmodules: Succeeded
> NOTE: Running task 1827 of 1849 (ID: 88, /home/filip/YOCTO_DISK/fsl-arm-bsp/sources/meta-fsl-filip/recipes-filip/linux-yocto-myproj/linux-yocto-myproj_3.10.bb, do_strip)
> NOTE: recipe linux-yocto-myproj-3.10.17+gitAUTOINC+db725c88c7-r1: task do_strip: Started
> -----------------------------------------------------------------------------------------------------------------------
>
> I have also attached the output in the mail.
>
> Filip.
>
> Did you try bitbake-layers show-recipes to see if your recipe is available ?
> You can also check your local.conf and machine.conf
>
>
> On 08/07/2014 02:56 PM, filip.ghimpeteanu@freescale.com wrote:
>> Hi Stephane,
>>
>> Yes I tried, but the build is done with the 3.15.0-rc2-yocto-standard
>>
>> Filip
>>
>> -----Original Message-----
>> From: scerveau [mailto:scerveau@gmail.com]
>> Sent: Thursday, August 07, 2014 3:14 PM
>> To: Ghimpeteanu Filip-B50611; meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] Can't select my own Kernel source
>>
>> Hello,
>>
>> Did you change your conf file with this ?
>> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto_myproj"
>>
>> BR.
>>
>> Stephane
>> On 08/07/2014 12:30 PM, filip.ghimpeteanu@freescale.com wrote:
>>> Hello,
>>>
>>> I am trying to build a custom kernel from local sources.
>>> I followed the instructions described in Lab4 of Tom Zanussi's and
>>> Darren Hart's "Hands-on Project" [1], but apparently the
>>> linux-timesys recipe executes instead of mine. The resulting kernel
>>> is 3.0.15 (the one specified by the linux-timesys) instead of mine
>>> which is 3.10.17
>>>
>>> How can I tell Bitbake to use the Kernel from my local sources?
>>>
>>>
>>> This is a snapshot of my recipe:
>>> ---------------------------------------------------------------------
>>> -
>>> --------
>>> .../meta-fsl-filip/recipes-filip/linux-yocto-myproj/linux-yocto-mypro
>>> j
>>> _3.10.bb
>>> ----------------------------------------
>>>
>>> inherit kernel
>>> require recipes-kernel/linux/linux-yocto.inc
>>>
>>> SRC_URI = "git:///home/filip/YOCTO_DISK/Kernels/linux-rayleigh;protocol=file;nocheckout=1"
>>> SRC_URI += "file://defconfig"
>>>
>>> KBRANCH = "fbdcu_dev"
>>>
>>> LINUX_VERSION ?= "3.10.17"
>>> LINUX_VERSION_EXTENSION ?= "-custom"
>>>
>>> SRCREV_machine="${AUTOREV}"
>>> SRCREV="${AUTOREV}"
>>>
>>> PR = "r0"
>>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> COMPATIBLE_MACHINE = "twr-vf65gs10"
>>> ----------------------------------------
>>>
>>> [1]: http://goo.gl/MQDzw6
>>>
>>> Thank you,
>>> Ghimpeteanu Filip.
>
>
>


  reply	other threads:[~2014-08-07 13:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 10:30 Can't select my own Kernel source filip.ghimpeteanu
2014-08-07 12:14 ` scerveau
     [not found]   ` <4afa01fb8465431d88c988a8e70af423@BLUPR03MB565.namprd03.prod.outlook.com>
     [not found]     ` <53E37CBD.6080904@gmail.com>
2014-08-07 13:38       ` filip.ghimpeteanu
2014-08-07 13:44         ` Gary Thomas [this message]
2014-08-07 14:00           ` filip.ghimpeteanu
2014-08-07 14:13             ` John Weber
2014-08-07 15:26               ` filip.ghimpeteanu
2014-08-07 18:22                 ` John Weber
2014-08-08  6:49                   ` filip.ghimpeteanu
2014-08-14 12:28                     ` Otavio Salvador
     [not found] <mailman.21522.1407435753.26702.meta-freescale@yoctoproject.org>
2014-08-07 19:27 ` mk
2014-08-08  7:05   ` filip.ghimpeteanu
2014-08-08 10:05   ` Max Krummenacher
2014-08-08 13:45     ` filip.ghimpeteanu
2014-08-08 13:53       ` Gary Thomas
2014-08-14 12:30       ` Otavio Salvador

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=53E382C2.7030304@gmail.com \
    --to=samoht.yrag@gmail.com \
    --cc=meta-freescale@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.