[bitbake-devel] source modification and re-build

nousi bnousilal at gmail.com
Wed Jul 27 06:13:19 UTC 2016


Hi,

kernel image name is "uImage-nousi-linux.img" in
"poky/build/tmp/deploy/images/nousi12k/" directory when I use "bitbake
nousi-dev-image", it will create all the images including rootfs,
u-boot, dtb and takes lot of time to build.

I would like to build only kernel image "uImage-nousi-linux.img".
Please, let me know how can I do it.

Thanks,
Nousi.


On Thu, Jul 21, 2016 at 4:56 PM, Jussi Kukkonen
<jussi.kukkonen at intel.com> wrote:
>
>
> On 21 July 2016 at 13:32, nousi <bnousilal at gmail.com> wrote:
>>
>> please, ignore my previous mail.
>> There was an issue with the option "-C", it should be "-c".
>>
>> I have compiled modified kernel using " bitbake -c compile -f nousi-linux"
>> command but, it seems kernel image does not get update with new
>> configuration at below path.
>>
>> "poky/build/tmp/deploy/images/nousi123k/"
>
>
> You forced a kernel compile only, after that you probably want to
> re-generate the image ("bitbake <image-name>").
>
> Note that this method of modifying kernel configuration is not how you'd do
> it in production: See
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#generating-configuration-files
> for how to create a defconfig or a config fragment and
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
> for configuring your kernel with them.
>
> Jussi
>
>>
>> Please, let me know if I am missing something in the process.
>>
>> On Thu, Jul 21, 2016 at 3:51 PM, nousi <bnousilal at gmail.com> wrote:
>>>
>>> Hi Zhenhua Luo,
>>>
>>> Could not able to compile the kernel after changing the kernel
>>> configuration using "bitbake -c menuconfig nousi-linux" command.
>>> Please, have a look at the console logs below.
>>>
>>> #bitbake -C compile –f nousi-linux
>>> NOTE: Preparing RunQueue
>>> NOTE: Tainting hash to force rebuild of task
>>> /projects/nousi-linux/nousilal/ns2/poky/build/../meta-nousi/common/recipes-kernel/linux/nousi-linux_0.0.0.bb,
>>> do_rm_work_all
>>> ERROR: Task do_compile is marked nostamp, cannot invalidate this task
>>> ERROR: An uncaught exception occured in runqueue, please see the failure
>>> below:
>>> ERROR: Running idle function
>>> Traceback (most recent call last):
>>>   File
>>> "/projects/nousi123-linux/nousilal/nn2/poky/bitbake/lib/bb/runqueue.py",
>>> line 1094, in RunQueue.execute_runqueue():
>>>              try:
>>>     >            return self._execute_runqueue()
>>>              except bb.runqueue.TaskFailure:
>>>   File
>>> "/projects/nousi123-linux/nousilal/nn2/poky/bitbake/lib/bb/runqueue.py",
>>> line 1029, in RunQueue._execute_runqueue():
>>>                  self.rqexe = RunQueueExecuteDummy(self)
>>>     >            if self.rqdata.prepare() == 0:
>>>                      self.state = runQueueComplete
>>>   File
>>> "/projects/nousi123-linux/nousilal/nn2/poky/bitbake/lib/bb/runqueue.py",
>>> line 796, in RunQueueData.prepare():
>>>                      for st in
>>> self.cooker.configuration.invalidate_stamp.split(','):
>>>     >                    invalidate_task(fn, "do_%s" % st, True)
>>>
>>>   File
>>> "/projects/nousi123-linux/nousilal/nn2/poky/bitbake/lib/bb/runqueue.py",
>>> line 780, in
>>> invalidate_task(fn='/projects/nousi123-linux/nousilal/nn2/poky/build/../meta-nousi/common/recipes-kernel/linux/nousi-linux_0.0.0.bb',
>>> taskname='do_compile', error_nostamp=True):
>>>                      if error_nostamp:
>>>     >                    bb.fatal("Task %s is marked nostamp, cannot
>>> invalidate this task" % taskname)
>>>                      else:
>>>   File
>>> "/projects/nousi123-linux/nousilal/nn2/poky/bitbake/lib/bb/__init__.py",
>>> line 102, in fatal:
>>>          logger.critical(''.join(args))
>>>     >    raise BBHandledException()
>>>
>>> BBHandledException
>>>
>>> On Thu, Jul 21, 2016 at 9:30 AM, Zhenhua Luo <zhenhua.luo at nxp.com> wrote:
>>>>
>>>> Hi Nousilal,
>>>>
>>>>
>>>>
>>>> “bitbake -c menuconfig nousi-linux” is used for changing the kernel
>>>> configs instead of modifying source code, you can run “bitbake -C compile -f
>>>> nousi-linux ” to force rebuild with updated kernel configs.
>>>>
>>>>
>>>>
>>>> To modify the source code, you can do it in
>>>> tmp/work-shared/<machine>/kernel-source/, then run “bitbake -C compile –f
>>>> nousi-linux” to rebuild new kernel image.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>>
>>>>
>>>> Zhenhua
>>>>
>>>>
>>>>
>>>> From: bitbake-devel-bounces at lists.openembedded.org
>>>> [mailto:bitbake-devel-bounces at lists.openembedded.org] On Behalf Of nousi
>>>> Sent: Wednesday, July 20, 2016 2:18 PM
>>>> To: bitbake-devel at lists.openembedded.org
>>>> Subject: [bitbake-devel] source modification and re-build
>>>>
>>>>
>>>>
>>>> Hi All,
>>>>
>>>>
>>>>
>>>> Am new to yocto environment, please let me know the process to change
>>>> kernel source using "bitbake nousi-linux -c menuconfig".
>>>>
>>>>
>>>>
>>>> I can able to make changes using "bitbake nousi-linux -c menuconfig"
>>>> this command but my changes were not included in the new re-built image.
>>>>
>>>> Am using the development linux source code.
>>>>
>>>> Any help is appreciated.
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Thanks & Regards,
>>>> B.Nousilal,
>>>
>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> B.Nousilal,
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> B.Nousilal,
>>
>>
>> --
>> _______________________________________________
>> bitbake-devel mailing list
>> bitbake-devel at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>>
>



-- 
Thanks & Regards,
B.Nousilal,



More information about the bitbake-devel mailing list