Hi Michael,

I had updated details in below stackoverflow post,
Hope it will help you,
http://stackoverflow.com/questions/30723261/building-robert-nelsons-linux-kernel-into-yoctodaisy-for-beaglebone-black

Thank you,

Regards,
Ankur

On Wed, Jan 20, 2016 at 7:09 PM, Michael Liesenberg
<mich...@liesenberg.biz> wrote:
>
> Hi Ankur,
>
> have you got it to work?
>
> How did you do?
>
>
> Am Montag, 8. Juni 2015 20:36:27 UTC+2 schrieb Ankur Tank:
>>
>> Hi Experts,
>>
>> I was trying to build Linux for beaglebone black from official repository
>> https://github.com/beagleboard/linux
>>
>> I am able to fetch and run menuconfig but when i try to compile the kernel
>> i get error.
>>
>> Following is the content of the recipe file.
>>
>> file name : linux-yocto-chipsee_3.14.bb
>> path: /home/ankur/yocto_daisy/poky/meta-ybdevelop/recipes-example/linux
>>
>> inherit kernel
>> require recipes-kernel/linux/linux-yocto.inc
>>
>> BRANCH = "3.14"
>> # Override SRC_URI in a bbappend file to point at a different source
>> # tree if you do not want to build from Linus' tree.
>> SRC_URI =
>> "git://github.com/beagleboard/linux.git;branch=${BRANCH};nocheckout=1;name=machine"
>>
>> LINUX_VERSION ?= "3.14"
>> LINUX_VERSION_EXTENSION ?= "-custom"
>>
>> # Override SRCREV to point to a different commit in a bbappend file to
>> # build a different release of the Linux kernel.
>> # tag: v3.4 76e10d158efb6d4516018846f60c2ab5501900bc
>> SRCREV_machine="76e10d158efb6d4516018846f60c2ab5501900bc"
>>
>> PR = "r1"
>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> # Override COMPATIBLE_MACHINE to include your machine in a bbappend
>> # file. Leaving it empty here ensures an early explicit build failure.
>> COMPATIBLE_MACHINE = "beaglebone"
>>
>> File name :linux-yocto-chipsee_3.14.bbappend
>> File path :
>> /home/ankur/yocto_daisy/poky/meta-ybdevelop/recipes-example/linux
>>
>> defconfig path:
>> /home/ankur/yocto_daisy/poky/meta-ybdevelop/recipes-example/linux/linux-yocto-chipsee_3.14
>>
>> With above configuration i am able to fetch and open menuconfig for
>> fetched linux kernel, command i used is as follows,
>>
>> -----Below command works----
>> # bitbake linux-yocto-chipsee -c menuconfig
>>
>> But when i try to compile linux using below command it gives error,
>> -----Below command gives below errors----
>> # bitbake linux-yocto-chipsee -c compile
>>
>>  /bin/sh: 1: arm-poky-linux-gnueabi-gcc: not found
>> | make[4]: *** [scripts/mod/empty.o] Error 127
>> | make[3]: *** [scripts/mod] Error 2
>> | make[3]: *** Waiting for unfinished jobs....
>> |   SHIPPED scripts/genksyms/lex.lex.c
>> |   Generating include/generated/mach-types.h
>> |   SHIPPED scripts/genksyms/keywords.hash.c
>> |   SHIPPED scripts/genksyms/parse.tab.h
>> |   SHIPPED scripts/genksyms/parse.tab.c
>> |   HOSTCC  scripts/genksyms/lex.lex.o
>> |   CC      kernel/bounds.s
>> | /bin/sh: 1: arm-poky-linux-gnueabi-gcc: not found
>>
>>
>> When i try to build using below command that time also it failed.
>>
>> -----Below command gives below errors along with previous error---
>> # bitbake linux-yocto-chipsee -c build
>>
>> ERROR: Multiple .bb files are due to be built which each provide
>> virtual/kernel
>> (/home/ankur/yocto_daisy/poky/meta-ybdevelop/recipes-example/linux/linux-yocto-chipsee_3.14.bb
>> /home/ankur/yocto_daisy/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb).
>>  This usually means one provides something the other doesn't and should.
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> ERROR: Function failed: do_compile (log file is located at
>> /home/ankur/yocto_daisy/poky/build_fresh/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto-chipsee/3.14+gitAUTOINC+76e10d158e-r1/temp/log.do_compile.30878)
>> ERROR: Logfile of failure stored in:
>> /home/ankur/yocto_daisy/poky/build_fresh/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto-chipsee/3.14+gitAUTOINC+76e10d158e-r1/temp/log.do_compile.30878
>>
>> Bitbake layers for linux shows below output
>>
>> # bitbake-layers show-recipes 'linux*'
>> Parsing recipes..done.
>> === Available recipes matching linux*: ===
>> linux-dummy:
>>   meta                 1.0
>> linux-firmware:
>>   meta                 1:0.0+gitAUTOINC+600caefd83
>> linux-libc-headers:
>>   meta                 3.14
>> linux-yocto:
>>   meta                 3.14.4+gitAUTOINC+183622e809_0143c6ebb4
>>   meta                 3.10 (skipped)
>>   meta                 3.4 (skipped)
>> linux-yocto-chipsee:
>>   meta-ybdevelop       3.14+gitAUTOINC+76e10d158e
>> linux-yocto-dev:
>>   meta                 unknown (skipped)
>> linux-yocto-rt:
>>   meta                 3.10 (skipped)
>>   meta                 3.14 (skipped)
>>   meta                 3.4 (skipped)
>> linux-yocto-tiny:
>>   meta                 3.10 (skipped)
>>   meta                 3.14 (skipped)
>>   meta                 3.4 (skipped)
>> linuxdoc-tools-native:
>>   meta                 0.9.69
>> linuxptp:
>>   meta-oe              1.4
>>
>> Any help/pointer/hint/suggestions to complete this ?
>>
>> Thank you,
>>
>> Regards,
>> Ankur
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/0SEmEFrltNI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to