* Getting error in linux-yocto kernel during build.
@ 2011-09-16 12:38 chinmaya hoshing
2011-09-16 14:24 ` Bruce Ashfield
2011-09-27 4:28 ` Darren Hart
0 siblings, 2 replies; 18+ messages in thread
From: chinmaya hoshing @ 2011-09-16 12:38 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Hi ,
I am building poky-build minimal live image for fishriver machine on 64 bit
host machine.
As I am having limited internet band-width, so I have identified all the
dependent packages and setup a Apache server on my local system so that I
can redirect the SRC_URI of all the packages to my local server.
I have changed the related recipes to build minimal live image, and modify
bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
packages I have tars which was present "build/download" folder.
While building linux-yocto, fetch and unpack was done but during kernel
checkout whatever git commits I have done previously in poky source were
flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
linux .
Following are the changes made in meta/recipes-kernel/linux/
linux-yocto_git.bb
#SRCREV_FORMAT = "meta_machine"
SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
// This tar file I took from
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
PV = "${LINUX_VERSION}"
In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
PREFERRED_VERSION_linux-yocto = "3.0" (which was
PREFERRED_VERSION_linux-yocto = "3.0+git%" )
Can any one help me to find the solution that if I had to pull linux kernel
source from tar file or such and not from git repository. What things I have
to do.
Regards
C Hoshing
[-- Attachment #2: Type: text/html, Size: 1992 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 12:38 Getting error in linux-yocto kernel during build chinmaya hoshing
@ 2011-09-16 14:24 ` Bruce Ashfield
2011-09-16 14:35 ` Bruce Ashfield
2011-09-27 4:28 ` Darren Hart
1 sibling, 1 reply; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-16 14:24 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing <cahoshing@gmail.com> wrote:
> Hi ,
> I am building poky-build minimal live image for fishriver machine on 64 bit
> host machine.
> As I am having limited internet band-width, so I have identified all the
> dependent packages and setup a Apache server on my local system so that I
> can redirect the SRC_URI of all the packages to my local server.
> I have changed the related recipes to build minimal live image, and modify
> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
> packages I have tars which was present "build/download" folder.
> While building linux-yocto, fetch and unpack was done but during kernel
> checkout whatever git commits I have done previously in poky source were
> flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
> linux .
>
> Following are the changes made in
> meta/recipes-kernel/linux/linux-yocto_git.bb
> #SRCREV_FORMAT = "meta_machine"
> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> // This tar file I took from
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> PV = "${LINUX_VERSION}"
> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>
> Can any one help me to find the solution that if I had to pull linux kernel
> source from tar file or such and not from git repository. What things I have
> to do.
The linux-yocto recipes are designed from the ground up to work on a git
based repository, and there's really no way to get around that fact (and no
plans to make any changes in this area).
So why not setup a git server, or put a local git repository on your build
machine and reference that ?
Bruce
> Regards
> C Hoshing
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 14:24 ` Bruce Ashfield
@ 2011-09-16 14:35 ` Bruce Ashfield
2011-09-16 15:06 ` Richard Purdie
0 siblings, 1 reply; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-16 14:35 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing <cahoshing@gmail.com> wrote:
>> Hi ,
>> I am building poky-build minimal live image for fishriver machine on 64 bit
>> host machine.
>> As I am having limited internet band-width, so I have identified all the
>> dependent packages and setup a Apache server on my local system so that I
>> can redirect the SRC_URI of all the packages to my local server.
>> I have changed the related recipes to build minimal live image, and modify
>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
>> packages I have tars which was present "build/download" folder.
>> While building linux-yocto, fetch and unpack was done but during kernel
>> checkout whatever git commits I have done previously in poky source were
>> flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
>> linux .
>>
>> Following are the changes made in
>> meta/recipes-kernel/linux/linux-yocto_git.bb
>> #SRCREV_FORMAT = "meta_machine"
>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
>> // This tar file I took from
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
>> PV = "${LINUX_VERSION}"
>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>>
>> Can any one help me to find the solution that if I had to pull linux kernel
>> source from tar file or such and not from git repository. What things I have
>> to do.
>
> The linux-yocto recipes are designed from the ground up to work on a git
> based repository, and there's really no way to get around that fact (and no
> plans to make any changes in this area).
Thinking further about this, if the tgz actually was just a tarball of the git
repositories (including the git blobs), it could work. But I'm not familiar with
the fetcher/bitbake internals in this area enough to know if this is possible.
Bruce
>
> So why not setup a git server, or put a local git repository on your build
> machine and reference that ?
>
> Bruce
>
>> Regards
>> C Hoshing
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 14:35 ` Bruce Ashfield
@ 2011-09-16 15:06 ` Richard Purdie
2011-09-16 15:11 ` Bruce Ashfield
2011-09-16 15:22 ` Gary Thomas
0 siblings, 2 replies; 18+ messages in thread
From: Richard Purdie @ 2011-09-16 15:06 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: poky, chinmaya hoshing
On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing <cahoshing@gmail.com> wrote:
> >> Hi ,
> >> I am building poky-build minimal live image for fishriver machine on 64 bit
> >> host machine.
> >> As I am having limited internet band-width, so I have identified all the
> >> dependent packages and setup a Apache server on my local system so that I
> >> can redirect the SRC_URI of all the packages to my local server.
> >> I have changed the related recipes to build minimal live image, and modify
> >> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
> >> packages I have tars which was present "build/download" folder.
> >> While building linux-yocto, fetch and unpack was done but during kernel
> >> checkout whatever git commits I have done previously in poky source were
> >> flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
> >> linux .
> >>
> >> Following are the changes made in
> >> meta/recipes-kernel/linux/linux-yocto_git.bb
> >> #SRCREV_FORMAT = "meta_machine"
> >> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> >> // This tar file I took from
> >> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> >> PV = "${LINUX_VERSION}"
> >> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
> >> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> >> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >>
> >> Can any one help me to find the solution that if I had to pull linux kernel
> >> source from tar file or such and not from git repository. What things I have
> >> to do.
> >
> > The linux-yocto recipes are designed from the ground up to work on a git
> > based repository, and there's really no way to get around that fact (and no
> > plans to make any changes in this area).
>
> Thinking further about this, if the tgz actually was just a tarball of the git
> repositories (including the git blobs), it could work.
This is exactly what we use behind the scenes for mirroring the git
repositories so this should work. It should be possible to use our
existing PREMIRROR code to avoid having to rewrite individual recipes
though.
It will firstly unpack the tarball, then access whether the revisions it
needs are present. If they're not, it will then (and only then) try and
fetch them over the network. If the tarball is complete it will
therefore not touch the network. If its incomplete it will only fetch
the different (delta).
Cheers,
Richard
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 15:06 ` Richard Purdie
@ 2011-09-16 15:11 ` Bruce Ashfield
2011-09-16 15:22 ` Gary Thomas
1 sibling, 0 replies; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-16 15:11 UTC (permalink / raw)
To: Richard Purdie; +Cc: poky, chinmaya hoshing
On 11-09-16 11:06 AM, Richard Purdie wrote:
> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>> <bruce.ashfield@gmail.com> wrote:
>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing<cahoshing@gmail.com> wrote:
>>>> Hi ,
>>>> I am building poky-build minimal live image for fishriver machine on 64 bit
>>>> host machine.
>>>> As I am having limited internet band-width, so I have identified all the
>>>> dependent packages and setup a Apache server on my local system so that I
>>>> can redirect the SRC_URI of all the packages to my local server.
>>>> I have changed the related recipes to build minimal live image, and modify
>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
>>>> packages I have tars which was present "build/download" folder.
>>>> While building linux-yocto, fetch and unpack was done but during kernel
>>>> checkout whatever git commits I have done previously in poky source were
>>>> flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
>>>> linux .
>>>>
>>>> Following are the changes made in
>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
>>>> #SRCREV_FORMAT = "meta_machine"
>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
>>>> // This tar file I took from
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
>>>> PV = "${LINUX_VERSION}"
>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>>>>
>>>> Can any one help me to find the solution that if I had to pull linux kernel
>>>> source from tar file or such and not from git repository. What things I have
>>>> to do.
>>>
>>> The linux-yocto recipes are designed from the ground up to work on a git
>>> based repository, and there's really no way to get around that fact (and no
>>> plans to make any changes in this area).
>>
>> Thinking further about this, if the tgz actually was just a tarball of the git
>> repositories (including the git blobs), it could work.
>
> This is exactly what we use behind the scenes for mirroring the git
> repositories so this should work. It should be possible to use our
> existing PREMIRROR code to avoid having to rewrite individual recipes
> though.
>
> It will firstly unpack the tarball, then access whether the revisions it
> needs are present. If they're not, it will then (and only then) try and
> fetch them over the network. If the tarball is complete it will
> therefore not touch the network. If its incomplete it will only fetch
> the different (delta).
That's what my slightly deeper look in the code told me as
well. As long as what lands in the working directory is the same,
the recipes don't care where it came from.
But should the preferred version have to change to pickup that
tarball ? That's the part that eludes me.
Bruce
>
> Cheers,
>
> Richard
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 15:06 ` Richard Purdie
2011-09-16 15:11 ` Bruce Ashfield
@ 2011-09-16 15:22 ` Gary Thomas
2011-09-20 9:51 ` chinmaya hoshing
1 sibling, 1 reply; 18+ messages in thread
From: Gary Thomas @ 2011-09-16 15:22 UTC (permalink / raw)
Cc: poky
On 2011-09-16 09:06, Richard Purdie wrote:
> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>> <bruce.ashfield@gmail.com> wrote:
>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing<cahoshing@gmail.com> wrote:
>>>> Hi ,
>>>> I am building poky-build minimal live image for fishriver machine on 64 bit
>>>> host machine.
>>>> As I am having limited internet band-width, so I have identified all the
>>>> dependent packages and setup a Apache server on my local system so that I
>>>> can redirect the SRC_URI of all the packages to my local server.
>>>> I have changed the related recipes to build minimal live image, and modify
>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
>>>> packages I have tars which was present "build/download" folder.
>>>> While building linux-yocto, fetch and unpack was done but during kernel
>>>> checkout whatever git commits I have done previously in poky source were
>>>> flashed out (lost), also the only recipe remains in meta/recipe-kernel/ is
>>>> linux .
>>>>
>>>> Following are the changes made in
>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
>>>> #SRCREV_FORMAT = "meta_machine"
>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
>>>> // This tar file I took from
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
>>>> PV = "${LINUX_VERSION}"
>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>>>>
>>>> Can any one help me to find the solution that if I had to pull linux kernel
>>>> source from tar file or such and not from git repository. What things I have
>>>> to do.
>>>
>>> The linux-yocto recipes are designed from the ground up to work on a git
>>> based repository, and there's really no way to get around that fact (and no
>>> plans to make any changes in this area).
>>
>> Thinking further about this, if the tgz actually was just a tarball of the git
>> repositories (including the git blobs), it could work.
>
> This is exactly what we use behind the scenes for mirroring the git
> repositories so this should work. It should be possible to use our
> existing PREMIRROR code to avoid having to rewrite individual recipes
> though.
>
> It will firstly unpack the tarball, then access whether the revisions it
> needs are present. If they're not, it will then (and only then) try and
> fetch them over the network. If the tarball is complete it will
> therefore not touch the network. If its incomplete it will only fetch
> the different (delta).
This does work as advertised - I use it exclusively. I have a local
package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
prove/protect that no network access is required.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 15:22 ` Gary Thomas
@ 2011-09-20 9:51 ` chinmaya hoshing
2011-09-20 13:54 ` Bruce Ashfield
2011-09-27 4:40 ` Darren Hart
0 siblings, 2 replies; 18+ messages in thread
From: chinmaya hoshing @ 2011-09-20 9:51 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 5790 bytes --]
Hi ,
I have set up a git server for linux-yocto.
Following is my recipe :
require linux-yocto.inc
KMACHINE = "yocto/standard/base"
KMACHINE_qemux86 = "yocto/standard/common-pc/base"
KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
KMACHINE_beagleboard = "yocto/standard/beagleboard"
KMACHINE_fishriver = "yocto/standard/fishriver"
KBRANCH = ${KMACHINE}
KMETA = meta
LINUX_VERSION ?= "3.0"
LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
PR = "r0"
#PV = "${LINUX_VERSION}+git${SRCPV}"
#SRCREV_FORMAT = "meta_machine"
SRC_URI =
"git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
COMPATIBLE_MACHINE =
"(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
# Functionality flags
KERNEL_REVISION_CHECKING ?= "t"
KERNEL_FEATURES="features/netfilter"
KERNEL_FEATURES_append_qemux86=" cfg/sound"
KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
YOCTO_KERNEL_META_DATA=t
# Temporary fix for oprofile and latencytop on qemux86-64
KERNEL_FEATURES_append_qemux86-64=" features/profiling"
KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
# extra tasks
addtask kernel_link_vmlinux after do_compile before do_install
addtask validate_branches before do_patch after do_kernel_checkout
addtask kernel_configcheck after do_configure before do_compile
require linux-tools.inc
But still I am getting the same result as before . My previous git commits
in poky source are flashed out , also the only recipe remains in
meta/recipe-kernel/ is linux .
Regards
C Hoshing
On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2011-09-16 09:06, Richard Purdie wrote:
>
>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>>
>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>>> <bruce.ashfield@gmail.com> wrote:
>>>
>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing<cahoshing@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi ,
>>>>> I am building poky-build minimal live image for fishriver machine on 64
>>>>> bit
>>>>> host machine.
>>>>> As I am having limited internet band-width, so I have identified all
>>>>> the
>>>>> dependent packages and setup a Apache server on my local system so that
>>>>> I
>>>>> can redirect the SRC_URI of all the packages to my local server.
>>>>> I have changed the related recipes to build minimal live image, and
>>>>> modify
>>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/**packages" , in
>>>>> side
>>>>> packages I have tars which was present "build/download" folder.
>>>>> While building linux-yocto, fetch and unpack was done but during kernel
>>>>> checkout whatever git commits I have done previously in poky source
>>>>> were
>>>>> flashed out (lost), also the only recipe remains in
>>>>> meta/recipe-kernel/ is
>>>>> linux .
>>>>>
>>>>> Following are the changes made in
>>>>> meta/recipes-kernel/linux/linu**x-yocto_git.bb<http://linux-yocto_git.bb>
>>>>> #SRCREV_FORMAT = "meta_machine"
>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-**3.0-3.0.tar.bz2"
>>>>> // This tar file I took from
>>>>> http://git.yoctoproject.org/**cgit/cgit.cgi/linux-yocto-3.0/**
>>>>> snapshot/linux-yocto-3.0-3.0.**tar.bz2<http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2>
>>>>> PV = "${LINUX_VERSION}"
>>>>> In file meta-intel/meta-fishriver/**conf/machine/fishriver.conf I
>>>>> modified
>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>>>>>
>>>>> Can any one help me to find the solution that if I had to pull linux
>>>>> kernel
>>>>> source from tar file or such and not from git repository. What things I
>>>>> have
>>>>> to do.
>>>>>
>>>>
>>>> The linux-yocto recipes are designed from the ground up to work on a git
>>>> based repository, and there's really no way to get around that fact (and
>>>> no
>>>> plans to make any changes in this area).
>>>>
>>>
>>> Thinking further about this, if the tgz actually was just a tarball of
>>> the git
>>> repositories (including the git blobs), it could work.
>>>
>>
>> This is exactly what we use behind the scenes for mirroring the git
>> repositories so this should work. It should be possible to use our
>> existing PREMIRROR code to avoid having to rewrite individual recipes
>> though.
>>
>> It will firstly unpack the tarball, then access whether the revisions it
>> needs are present. If they're not, it will then (and only then) try and
>> fetch them over the network. If the tarball is complete it will
>> therefore not touch the network. If its incomplete it will only fetch
>> the different (delta).
>>
>
> This does work as advertised - I use it exclusively. I have a local
> package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
> prove/protect that no network access is required.
>
> --
> ------------------------------**------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------**------------------------------
>
> ______________________________**_________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>
>
[-- Attachment #2: Type: text/html, Size: 7868 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-20 9:51 ` chinmaya hoshing
@ 2011-09-20 13:54 ` Bruce Ashfield
2011-09-21 4:49 ` chinmaya hoshing
2011-09-27 4:40 ` Darren Hart
1 sibling, 1 reply; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-20 13:54 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing <cahoshing@gmail.com> wrote:
> Hi ,
> I have set up a git server for linux-yocto.
> Following is my recipe :
> require linux-yocto.inc
> KMACHINE = "yocto/standard/base"
> KMACHINE_qemux86 = "yocto/standard/common-pc/base"
> KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
> KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
> KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
> KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
> KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
> KMACHINE_beagleboard = "yocto/standard/beagleboard"
> KMACHINE_fishriver = "yocto/standard/fishriver"
> KBRANCH = ${KMACHINE}
> KMETA = meta
> LINUX_VERSION ?= "3.0"
> LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> PR = "r0"
> #PV = "${LINUX_VERSION}+git${SRCPV}"
> #SRCREV_FORMAT = "meta_machine"
> SRC_URI =
> "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
>
> COMPATIBLE_MACHINE =
> "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
> # Functionality flags
> KERNEL_REVISION_CHECKING ?= "t"
> KERNEL_FEATURES="features/netfilter"
> KERNEL_FEATURES_append_qemux86=" cfg/sound"
> KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> YOCTO_KERNEL_META_DATA=t
> # Temporary fix for oprofile and latencytop on qemux86-64
> KERNEL_FEATURES_append_qemux86-64=" features/profiling"
> KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
> # extra tasks
> addtask kernel_link_vmlinux after do_compile before do_install
> addtask validate_branches before do_patch after do_kernel_checkout
> addtask kernel_configcheck after do_configure before do_compile
> require linux-tools.inc
>
>
> But still I am getting the same result as before . My previous git commits
> in poky source are flashed out , also the only recipe remains in
> meta/recipe-kernel/ is linux .
Just so I'm clear here. Are you still working with tarballs of the
source, or have
you setup a git server that is a clone of the linux-yocto-3.0 (as an
example) tree ?
Where are you putting your changes in this scenario ?
Bruce
>
> Regards
> C Hoshing
>
> On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>
>> On 2011-09-16 09:06, Richard Purdie wrote:
>>>
>>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>>>>
>>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>>>> <bruce.ashfield@gmail.com> wrote:
>>>>>
>>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing<cahoshing@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi ,
>>>>>> I am building poky-build minimal live image for fishriver machine on
>>>>>> 64 bit
>>>>>> host machine.
>>>>>> As I am having limited internet band-width, so I have identified all
>>>>>> the
>>>>>> dependent packages and setup a Apache server on my local system so
>>>>>> that I
>>>>>> can redirect the SRC_URI of all the packages to my local server.
>>>>>> I have changed the related recipes to build minimal live image, and
>>>>>> modify
>>>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in side
>>>>>> packages I have tars which was present "build/download" folder.
>>>>>> While building linux-yocto, fetch and unpack was done but during
>>>>>> kernel
>>>>>> checkout whatever git commits I have done previously in poky source
>>>>>> were
>>>>>> flashed out (lost), also the only recipe remains in
>>>>>> meta/recipe-kernel/ is
>>>>>> linux .
>>>>>>
>>>>>> Following are the changes made in
>>>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
>>>>>> #SRCREV_FORMAT = "meta_machine"
>>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
>>>>>> // This tar file I took from
>>>>>>
>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
>>>>>> PV = "${LINUX_VERSION}"
>>>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I
>>>>>> modified
>>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>>>>>>
>>>>>> Can any one help me to find the solution that if I had to pull linux
>>>>>> kernel
>>>>>> source from tar file or such and not from git repository. What things
>>>>>> I have
>>>>>> to do.
>>>>>
>>>>> The linux-yocto recipes are designed from the ground up to work on a
>>>>> git
>>>>> based repository, and there's really no way to get around that fact
>>>>> (and no
>>>>> plans to make any changes in this area).
>>>>
>>>> Thinking further about this, if the tgz actually was just a tarball of
>>>> the git
>>>> repositories (including the git blobs), it could work.
>>>
>>> This is exactly what we use behind the scenes for mirroring the git
>>> repositories so this should work. It should be possible to use our
>>> existing PREMIRROR code to avoid having to rewrite individual recipes
>>> though.
>>>
>>> It will firstly unpack the tarball, then access whether the revisions it
>>> needs are present. If they're not, it will then (and only then) try and
>>> fetch them over the network. If the tarball is complete it will
>>> therefore not touch the network. If its incomplete it will only fetch
>>> the different (delta).
>>
>> This does work as advertised - I use it exclusively. I have a local
>> package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
>> prove/protect that no network access is required.
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas | Consulting for the
>> MLB Associates | Embedded world
>> ------------------------------------------------------------
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-20 13:54 ` Bruce Ashfield
@ 2011-09-21 4:49 ` chinmaya hoshing
2011-09-21 12:30 ` Bruce Ashfield
0 siblings, 1 reply; 18+ messages in thread
From: chinmaya hoshing @ 2011-09-21 4:49 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: poky
[-- Attachment #1: Type: text/plain, Size: 6896 bytes --]
Hi ,
I have setup a git server that is clone of linux-yocto-3.0 from
git://git.yoctoproject.org/linux-yocto-3.0 repository.
Regards
C Hoshing
On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield <bruce.ashfield@gmail.com>wrote:
> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing <cahoshing@gmail.com>
> wrote:
> > Hi ,
> > I have set up a git server for linux-yocto.
> > Following is my recipe :
> > require linux-yocto.inc
> > KMACHINE = "yocto/standard/base"
> > KMACHINE_qemux86 = "yocto/standard/common-pc/base"
> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> > KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> > KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
> > KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
> > KMACHINE_fishriver = "yocto/standard/fishriver"
> > KBRANCH = ${KMACHINE}
> > KMETA = meta
> > LINUX_VERSION ?= "3.0"
> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> > PR = "r0"
> > #PV = "${LINUX_VERSION}+git${SRCPV}"
> > #SRCREV_FORMAT = "meta_machine"
> > SRC_URI =
> >
> "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
> >
> > COMPATIBLE_MACHINE =
> >
> "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
> > # Functionality flags
> > KERNEL_REVISION_CHECKING ?= "t"
> > KERNEL_FEATURES="features/netfilter"
> > KERNEL_FEATURES_append_qemux86=" cfg/sound"
> > KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> > YOCTO_KERNEL_META_DATA=t
> > # Temporary fix for oprofile and latencytop on qemux86-64
> > KERNEL_FEATURES_append_qemux86-64=" features/profiling"
> > KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
> > # extra tasks
> > addtask kernel_link_vmlinux after do_compile before do_install
> > addtask validate_branches before do_patch after do_kernel_checkout
> > addtask kernel_configcheck after do_configure before do_compile
> > require linux-tools.inc
> >
> >
> > But still I am getting the same result as before . My previous git
> commits
> > in poky source are flashed out , also the only recipe remains in
> > meta/recipe-kernel/ is linux .
>
> Just so I'm clear here. Are you still working with tarballs of the
> source, or have
> you setup a git server that is a clone of the linux-yocto-3.0 (as an
> example) tree ?
>
> Where are you putting your changes in this scenario ?
>
> Bruce
>
> >
> > Regards
> > C Hoshing
> >
> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> >>
> >> On 2011-09-16 09:06, Richard Purdie wrote:
> >>>
> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
> >>>>
> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
> >>>> <bruce.ashfield@gmail.com> wrote:
> >>>>>
> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya hoshing<
> cahoshing@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hi ,
> >>>>>> I am building poky-build minimal live image for fishriver machine on
> >>>>>> 64 bit
> >>>>>> host machine.
> >>>>>> As I am having limited internet band-width, so I have identified all
> >>>>>> the
> >>>>>> dependent packages and setup a Apache server on my local system so
> >>>>>> that I
> >>>>>> can redirect the SRC_URI of all the packages to my local server.
> >>>>>> I have changed the related recipes to build minimal live image, and
> >>>>>> modify
> >>>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
> side
> >>>>>> packages I have tars which was present "build/download" folder.
> >>>>>> While building linux-yocto, fetch and unpack was done but during
> >>>>>> kernel
> >>>>>> checkout whatever git commits I have done previously in poky source
> >>>>>> were
> >>>>>> flashed out (lost), also the only recipe remains in
> >>>>>> meta/recipe-kernel/ is
> >>>>>> linux .
> >>>>>>
> >>>>>> Following are the changes made in
> >>>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
> >>>>>> #SRCREV_FORMAT = "meta_machine"
> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> >>>>>> // This tar file I took from
> >>>>>>
> >>>>>>
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> >>>>>> PV = "${LINUX_VERSION}"
> >>>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I
> >>>>>> modified
> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >>>>>>
> >>>>>> Can any one help me to find the solution that if I had to pull linux
> >>>>>> kernel
> >>>>>> source from tar file or such and not from git repository. What
> things
> >>>>>> I have
> >>>>>> to do.
> >>>>>
> >>>>> The linux-yocto recipes are designed from the ground up to work on a
> >>>>> git
> >>>>> based repository, and there's really no way to get around that fact
> >>>>> (and no
> >>>>> plans to make any changes in this area).
> >>>>
> >>>> Thinking further about this, if the tgz actually was just a tarball of
> >>>> the git
> >>>> repositories (including the git blobs), it could work.
> >>>
> >>> This is exactly what we use behind the scenes for mirroring the git
> >>> repositories so this should work. It should be possible to use our
> >>> existing PREMIRROR code to avoid having to rewrite individual recipes
> >>> though.
> >>>
> >>> It will firstly unpack the tarball, then access whether the revisions
> it
> >>> needs are present. If they're not, it will then (and only then) try and
> >>> fetch them over the network. If the tarball is complete it will
> >>> therefore not touch the network. If its incomplete it will only fetch
> >>> the different (delta).
> >>
> >> This does work as advertised - I use it exclusively. I have a local
> >> package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
> >> prove/protect that no network access is required.
> >>
> >> --
> >> ------------------------------------------------------------
> >> Gary Thomas | Consulting for the
> >> MLB Associates | Embedded world
> >> ------------------------------------------------------------
> >> _______________________________________________
> >> poky mailing list
> >> poky@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/poky
> >
> >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/poky
> >
> >
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
[-- Attachment #2: Type: text/html, Size: 10029 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-21 4:49 ` chinmaya hoshing
@ 2011-09-21 12:30 ` Bruce Ashfield
2011-09-21 14:03 ` chinmaya hoshing
0 siblings, 1 reply; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-21 12:30 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On Wed, Sep 21, 2011 at 12:49 AM, chinmaya hoshing <cahoshing@gmail.com> wrote:
> Hi ,
> I have setup a git server that is clone of linux-yocto-3.0 from
> git://git.yoctoproject.org/linux-yocto-3.0 repository.
That's good! So where are you pushing your changes ? To that repo ? Are
you updating the SRCREV or using AUTOREV in your local layers ? I use
this workflow everyday, so it does work. I just need to understand where you
are putting your changes, and then we'll know why you aren't seeing them
on subsequent builds (or we'll have more ideas about where to look).
Cheers,
Bruce
> Regards
> C Hoshing
>
> On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>>
>> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing <cahoshing@gmail.com>
>> wrote:
>> > Hi ,
>> > I have set up a git server for linux-yocto.
>> > Following is my recipe :
>> > require linux-yocto.inc
>> > KMACHINE = "yocto/standard/base"
>> > KMACHINE_qemux86 = "yocto/standard/common-pc/base"
>> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
>> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
>> > KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
>> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
>> > KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
>> > KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
>> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
>> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
>> > KMACHINE_fishriver = "yocto/standard/fishriver"
>> > KBRANCH = ${KMACHINE}
>> > KMETA = meta
>> > LINUX_VERSION ?= "3.0"
>> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
>> > PR = "r0"
>> > #PV = "${LINUX_VERSION}+git${SRCPV}"
>> > #SRCREV_FORMAT = "meta_machine"
>> > SRC_URI =
>> >
>> > "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
>> >
>> > COMPATIBLE_MACHINE =
>> >
>> > "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
>> > # Functionality flags
>> > KERNEL_REVISION_CHECKING ?= "t"
>> > KERNEL_FEATURES="features/netfilter"
>> > KERNEL_FEATURES_append_qemux86=" cfg/sound"
>> > KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
>> > YOCTO_KERNEL_META_DATA=t
>> > # Temporary fix for oprofile and latencytop on qemux86-64
>> > KERNEL_FEATURES_append_qemux86-64=" features/profiling"
>> > KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
>> > # extra tasks
>> > addtask kernel_link_vmlinux after do_compile before do_install
>> > addtask validate_branches before do_patch after do_kernel_checkout
>> > addtask kernel_configcheck after do_configure before do_compile
>> > require linux-tools.inc
>> >
>> >
>> > But still I am getting the same result as before . My previous git
>> > commits
>> > in poky source are flashed out , also the only recipe remains in
>> > meta/recipe-kernel/ is linux .
>>
>> Just so I'm clear here. Are you still working with tarballs of the
>> source, or have
>> you setup a git server that is a clone of the linux-yocto-3.0 (as an
>> example) tree ?
>>
>> Where are you putting your changes in this scenario ?
>>
>> Bruce
>>
>> >
>> > Regards
>> > C Hoshing
>> >
>> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> >>
>> >> On 2011-09-16 09:06, Richard Purdie wrote:
>> >>>
>> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>> >>>>
>> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>> >>>> <bruce.ashfield@gmail.com> wrote:
>> >>>>>
>> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya
>> >>>>> hoshing<cahoshing@gmail.com>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>> Hi ,
>> >>>>>> I am building poky-build minimal live image for fishriver machine
>> >>>>>> on
>> >>>>>> 64 bit
>> >>>>>> host machine.
>> >>>>>> As I am having limited internet band-width, so I have identified
>> >>>>>> all
>> >>>>>> the
>> >>>>>> dependent packages and setup a Apache server on my local system so
>> >>>>>> that I
>> >>>>>> can redirect the SRC_URI of all the packages to my local server.
>> >>>>>> I have changed the related recipes to build minimal live image,
>> >>>>>> and
>> >>>>>> modify
>> >>>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
>> >>>>>> side
>> >>>>>> packages I have tars which was present "build/download" folder.
>> >>>>>> While building linux-yocto, fetch and unpack was done but during
>> >>>>>> kernel
>> >>>>>> checkout whatever git commits I have done previously in poky source
>> >>>>>> were
>> >>>>>> flashed out (lost), also the only recipe remains in
>> >>>>>> meta/recipe-kernel/ is
>> >>>>>> linux .
>> >>>>>>
>> >>>>>> Following are the changes made in
>> >>>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
>> >>>>>> #SRCREV_FORMAT = "meta_machine"
>> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
>> >>>>>> // This tar file I took from
>> >>>>>>
>> >>>>>>
>> >>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
>> >>>>>> PV = "${LINUX_VERSION}"
>> >>>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I
>> >>>>>> modified
>> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>> >>>>>>
>> >>>>>> Can any one help me to find the solution that if I had to pull
>> >>>>>> linux
>> >>>>>> kernel
>> >>>>>> source from tar file or such and not from git repository. What
>> >>>>>> things
>> >>>>>> I have
>> >>>>>> to do.
>> >>>>>
>> >>>>> The linux-yocto recipes are designed from the ground up to work on a
>> >>>>> git
>> >>>>> based repository, and there's really no way to get around that fact
>> >>>>> (and no
>> >>>>> plans to make any changes in this area).
>> >>>>
>> >>>> Thinking further about this, if the tgz actually was just a tarball
>> >>>> of
>> >>>> the git
>> >>>> repositories (including the git blobs), it could work.
>> >>>
>> >>> This is exactly what we use behind the scenes for mirroring the git
>> >>> repositories so this should work. It should be possible to use our
>> >>> existing PREMIRROR code to avoid having to rewrite individual recipes
>> >>> though.
>> >>>
>> >>> It will firstly unpack the tarball, then access whether the revisions
>> >>> it
>> >>> needs are present. If they're not, it will then (and only then) try
>> >>> and
>> >>> fetch them over the network. If the tarball is complete it will
>> >>> therefore not touch the network. If its incomplete it will only fetch
>> >>> the different (delta).
>> >>
>> >> This does work as advertised - I use it exclusively. I have a local
>> >> package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
>> >> prove/protect that no network access is required.
>> >>
>> >> --
>> >> ------------------------------------------------------------
>> >> Gary Thomas | Consulting for the
>> >> MLB Associates | Embedded world
>> >> ------------------------------------------------------------
>> >> _______________________________________________
>> >> poky mailing list
>> >> poky@yoctoproject.org
>> >> https://lists.yoctoproject.org/listinfo/poky
>> >
>> >
>> > _______________________________________________
>> > poky mailing list
>> > poky@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/poky
>> >
>> >
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-21 12:30 ` Bruce Ashfield
@ 2011-09-21 14:03 ` chinmaya hoshing
2011-09-21 16:10 ` Bruce Ashfield
0 siblings, 1 reply; 18+ messages in thread
From: chinmaya hoshing @ 2011-09-21 14:03 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: poky
[-- Attachment #1.1: Type: text/plain, Size: 9889 bytes --]
Hi ,
I am not doing any changes to kernel, following are the thing what I did :-
1. I cloned poky from ( git://git.yoctoproject.org/poky ) and using
bernard<http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=bernard>
branch.
2. I pull some packages from openembeded and also create my own.
3. I maintained git repository for my poky source and did git commit for all
for my changes.
4. I created a local git and ftp repo on my local machine and modify the
related recipes (SRC_URI ) as I don't want to waste my band width by
downloaing packages while building again and again.
Now I have a local the git repository for linux-yocto from
git://git.yoctoproject.org/linux-yocto-3.0
<git://git.yoctoproject.org/linux-yocto-3.0>
Now I modify the linux-yocto_git.bb as follows :-
- git://
git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
+ git://
192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
Every package is building fine even u-boot but, while building linux-yocto I
got error as "No such file or directory update-modules, scripts/bitbake " (
some more dirs ).
When I examine the source tree for poky I found out that linux-yocto source
is fetched in side the poky source and modifying the poky source tree.
The modification also removing the poky recipes directories like
recipes-multimedia
recipes-sato and so on .
I am also attaching the tree for both i.e original poky tree and after
pulling linux-yocto poky tree
Regards
Chinmaya
On Wed, Sep 21, 2011 at 6:00 PM, Bruce Ashfield <bruce.ashfield@gmail.com>wrote:
> On Wed, Sep 21, 2011 at 12:49 AM, chinmaya hoshing <cahoshing@gmail.com>
> wrote:
> > Hi ,
> > I have setup a git server that is clone of linux-yocto-3.0 from
> > git://git.yoctoproject.org/linux-yocto-3.0 repository.
>
> That's good! So where are you pushing your changes ? To that repo ? Are
> you updating the SRCREV or using AUTOREV in your local layers ? I use
> this workflow everyday, so it does work. I just need to understand where
> you
> are putting your changes, and then we'll know why you aren't seeing them
> on subsequent builds (or we'll have more ideas about where to look).
>
> Cheers,
>
> Bruce
>
> > Regards
> > C Hoshing
> >
> > On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield <
> bruce.ashfield@gmail.com>
> > wrote:
> >>
> >> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing <cahoshing@gmail.com>
> >> wrote:
> >> > Hi ,
> >> > I have set up a git server for linux-yocto.
> >> > Following is my recipe :
> >> > require linux-yocto.inc
> >> > KMACHINE = "yocto/standard/base"
> >> > KMACHINE_qemux86 = "yocto/standard/common-pc/base"
> >> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
> >> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> >> > KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
> >> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> >> > KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
> >> > KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
> >> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
> >> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
> >> > KMACHINE_fishriver = "yocto/standard/fishriver"
> >> > KBRANCH = ${KMACHINE}
> >> > KMETA = meta
> >> > LINUX_VERSION ?= "3.0"
> >> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> >> > PR = "r0"
> >> > #PV = "${LINUX_VERSION}+git${SRCPV}"
> >> > #SRCREV_FORMAT = "meta_machine"
> >> > SRC_URI =
> >> >
> >> >
> "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
> >> >
> >> > COMPATIBLE_MACHINE =
> >> >
> >> >
> "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
> >> > # Functionality flags
> >> > KERNEL_REVISION_CHECKING ?= "t"
> >> > KERNEL_FEATURES="features/netfilter"
> >> > KERNEL_FEATURES_append_qemux86=" cfg/sound"
> >> > KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> >> > YOCTO_KERNEL_META_DATA=t
> >> > # Temporary fix for oprofile and latencytop on qemux86-64
> >> > KERNEL_FEATURES_append_qemux86-64=" features/profiling"
> >> > KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
> >> > # extra tasks
> >> > addtask kernel_link_vmlinux after do_compile before do_install
> >> > addtask validate_branches before do_patch after do_kernel_checkout
> >> > addtask kernel_configcheck after do_configure before do_compile
> >> > require linux-tools.inc
> >> >
> >> >
> >> > But still I am getting the same result as before . My previous git
> >> > commits
> >> > in poky source are flashed out , also the only recipe remains in
> >> > meta/recipe-kernel/ is linux .
> >>
> >> Just so I'm clear here. Are you still working with tarballs of the
> >> source, or have
> >> you setup a git server that is a clone of the linux-yocto-3.0 (as an
> >> example) tree ?
> >>
> >> Where are you putting your changes in this scenario ?
> >>
> >> Bruce
> >>
> >> >
> >> > Regards
> >> > C Hoshing
> >> >
> >> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas <gary@mlbassoc.com>
> wrote:
> >> >>
> >> >> On 2011-09-16 09:06, Richard Purdie wrote:
> >> >>>
> >> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
> >> >>>>
> >> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
> >> >>>> <bruce.ashfield@gmail.com> wrote:
> >> >>>>>
> >> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya
> >> >>>>> hoshing<cahoshing@gmail.com>
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> Hi ,
> >> >>>>>> I am building poky-build minimal live image for fishriver machine
> >> >>>>>> on
> >> >>>>>> 64 bit
> >> >>>>>> host machine.
> >> >>>>>> As I am having limited internet band-width, so I have identified
> >> >>>>>> all
> >> >>>>>> the
> >> >>>>>> dependent packages and setup a Apache server on my local system
> so
> >> >>>>>> that I
> >> >>>>>> can redirect the SRC_URI of all the packages to my local server.
> >> >>>>>> I have changed the related recipes to build minimal live image,
> >> >>>>>> and
> >> >>>>>> modify
> >> >>>>>> bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
> >> >>>>>> side
> >> >>>>>> packages I have tars which was present "build/download" folder.
> >> >>>>>> While building linux-yocto, fetch and unpack was done but during
> >> >>>>>> kernel
> >> >>>>>> checkout whatever git commits I have done previously in poky
> source
> >> >>>>>> were
> >> >>>>>> flashed out (lost), also the only recipe remains in
> >> >>>>>> meta/recipe-kernel/ is
> >> >>>>>> linux .
> >> >>>>>>
> >> >>>>>> Following are the changes made in
> >> >>>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
> >> >>>>>> #SRCREV_FORMAT = "meta_machine"
> >> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> >> >>>>>> // This tar file I took from
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> >> >>>>>> PV = "${LINUX_VERSION}"
> >> >>>>>> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I
> >> >>>>>> modified
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >> >>>>>>
> >> >>>>>> Can any one help me to find the solution that if I had to pull
> >> >>>>>> linux
> >> >>>>>> kernel
> >> >>>>>> source from tar file or such and not from git repository. What
> >> >>>>>> things
> >> >>>>>> I have
> >> >>>>>> to do.
> >> >>>>>
> >> >>>>> The linux-yocto recipes are designed from the ground up to work on
> a
> >> >>>>> git
> >> >>>>> based repository, and there's really no way to get around that
> fact
> >> >>>>> (and no
> >> >>>>> plans to make any changes in this area).
> >> >>>>
> >> >>>> Thinking further about this, if the tgz actually was just a tarball
> >> >>>> of
> >> >>>> the git
> >> >>>> repositories (including the git blobs), it could work.
> >> >>>
> >> >>> This is exactly what we use behind the scenes for mirroring the git
> >> >>> repositories so this should work. It should be possible to use our
> >> >>> existing PREMIRROR code to avoid having to rewrite individual
> recipes
> >> >>> though.
> >> >>>
> >> >>> It will firstly unpack the tarball, then access whether the
> revisions
> >> >>> it
> >> >>> needs are present. If they're not, it will then (and only then) try
> >> >>> and
> >> >>> fetch them over the network. If the tarball is complete it will
> >> >>> therefore not touch the network. If its incomplete it will only
> fetch
> >> >>> the different (delta).
> >> >>
> >> >> This does work as advertised - I use it exclusively. I have a local
> >> >> package cache which I use with PREMIRROR and I set BB_NO_NETWORK to
> >> >> prove/protect that no network access is required.
> >> >>
> >> >> --
> >> >> ------------------------------------------------------------
> >> >> Gary Thomas | Consulting for the
> >> >> MLB Associates | Embedded world
> >> >> ------------------------------------------------------------
> >> >> _______________________________________________
> >> >> poky mailing list
> >> >> poky@yoctoproject.org
> >> >> https://lists.yoctoproject.org/listinfo/poky
> >> >
> >> >
> >> > _______________________________________________
> >> > poky mailing list
> >> > poky@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/poky
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> "Thou shalt not follow the NULL pointer, for chaos and madness await
> >> thee at its end"
> >
> >
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
[-- Attachment #1.2: Type: text/html, Size: 16888 bytes --]
[-- Attachment #2: original_tree.log --]
[-- Type: text/x-log, Size: 11972 bytes --]
.
|-- bitbake
| |-- bin
| |-- contrib
| | `-- vim
| |-- doc
| | `-- manual
| `-- lib
| |-- bb
| `-- ply
|-- build
| |-- conf
| |-- downloads
| | `-- git2
| |-- sstate-cache
| `-- tmp
| |-- buildstats
| |-- cache
| |-- deploy
| |-- pkgdata
| |-- sstate-control
| |-- stamps
| |-- sysroots
| `-- work
|-- documentation
| |-- adt-manual
| | `-- figures
| |-- bsp-guide
| | `-- figures
| |-- kernel-manual
| | `-- figures
| |-- poky-ref-manual
| | |-- examples
| | |-- figures
| | `-- screenshots
| |-- template
| |-- tools
| `-- yocto-project-qs
| `-- figures
|-- meta
| |-- classes
| |-- conf
| | |-- distro
| | |-- machine
| | |-- machine-sdk
| | `-- swabber
| |-- files
| | `-- common-licenses
| |-- lib
| | `-- oe
| |-- recipes-bsp
| | |-- acpid
| | |-- apmd
| | |-- eee-acpi-scripts
| | |-- formfactor
| | |-- grub
| | |-- hostap
| | |-- keymaps
| | |-- libacpi
| | |-- lrzsz
| | |-- orinoco
| | |-- pciutils
| | |-- pcmciautils
| | |-- pm-utils
| | |-- pointercal
| | |-- powervr-drivers
| | |-- qemu-config
| | |-- setserial
| | |-- uboot
| | |-- usbinit
| | |-- usbutils
| | |-- v86d
| | |-- x-load
| | `-- zaurusd
| |-- recipes-connectivity
| | |-- avahi
| | |-- bind
| | |-- bluez
| | |-- chrome
| | |-- connman
| | |-- dhcp
| | |-- galago
| | |-- gsm
| | |-- gupnp
| | |-- gypsy
| | |-- iproute2
| | |-- irda-utils
| | |-- libnss-mdns
| | |-- libpcap
| | |-- libselinux
| | |-- libsepol
| | |-- mozilla
| | |-- nfs-utils
| | |-- ofono
| | |-- openssh
| | |-- openssl
| | |-- portmap
| | |-- ppp
| | |-- ppp-dialin
| | |-- resolvconf
| | |-- samba
| | |-- talloc
| | |-- telepathy
| | |-- wireless-tools
| | |-- wpa-supplicant
| | `-- zeroconf
| |-- recipes-core
| | |-- base-files
| | |-- base-passwd
| | |-- busybox
| | |-- console-tools
| | |-- coreutils
| | |-- dbus
| | |-- dbus-wait
| | |-- d-feet
| | |-- d-feet_test
| | |-- dropbear
| | |-- eggdbus
| | |-- eglibc
| | |-- erlang
| | |-- expat
| | |-- feed-config
| | |-- gettext
| | |-- glib-2.0
| | |-- glibc
| | |-- images
| | |-- initrdscripts
| | |-- initscripts
| | |-- jpeg
| | |-- libxml
| | |-- meta
| | |-- ncurses
| | |-- netbase
| | |-- notification-daemon
| | |-- psplash
| | |-- readline
| | |-- site_config
| | |-- sysfsutils
| | |-- sysvinit
| | |-- tasks
| | |-- tinylogin
| | |-- uclibc
| | |-- udev
| | |-- unionfs
| | |-- update-rc.d
| | |-- util-linux
| | `-- zlib
| |-- recipes-devtools
| | |-- apt
| | |-- autoconf
| | |-- automake
| | |-- binutils
| | |-- bison
| | |-- cdrtools
| | |-- chrpath
| | |-- cmake
| | |-- desktop-file-utils
| | |-- diffstat
| | |-- distcc
| | |-- docbook-dsssl-stylesheets
| | |-- docbook-sgml-dtd
| | |-- docbook-utils
| | |-- dosfstools
| | |-- dpkg
| | |-- e2fsprogs
| | |-- elfutils
| | |-- file
| | |-- flex
| | |-- gcc
| | |-- gdb
| | |-- genext2fs
| | |-- git
| | |-- gnu-config
| | |-- guilt
| | |-- icon-naming-utils
| | |-- insserv
| | |-- installer
| | |-- intltool
| | |-- libtool
| | |-- linuxdoc-tools
| | |-- m4
| | |-- make
| | |-- makedevs
| | |-- mklibs
| | |-- mtd
| | |-- mtools
| | |-- nasm
| | |-- openjade
| | |-- opensp
| | |-- opkg
| | |-- opkg-utils
| | |-- patch
| | |-- pax-utils
| | |-- perl
| | |-- pkgconfig
| | |-- prelink
| | |-- pseudo
| | |-- python
| | |-- qemu
| | |-- quilt
| | |-- rpm
| | |-- rsync
| | |-- sgml-common
| | |-- sgmlspl
| | |-- strace
| | |-- subversion
| | |-- swabber
| | |-- syslinux
| | |-- tcf-agent
| | |-- tcltk
| | |-- transfig
| | |-- ubootchart
| | |-- unfs-server
| | |-- unifdef
| | |-- update-alternatives
| | |-- valgrind
| | `-- yaffs2
| |-- recipes-extended
| | |-- at
| | |-- augeas
| | |-- bash
| | |-- bc
| | |-- blktool
| | |-- byacc
| | |-- bzip2
| | |-- chkconfig
| | |-- chrome-init
| | |-- cpio
| | |-- cracklib
| | |-- cronie
| | |-- cups
| | |-- cwautomacros
| | |-- diffutils
| | |-- ed
| | |-- ethtool
| | |-- findutils
| | |-- gamin
| | |-- gawk
| | |-- gperf
| | |-- grep
| | |-- groff
| | |-- gzip
| | |-- hdparm
| | |-- images
| | |-- install-recovery
| | |-- iptables
| | |-- iputils
| | |-- less
| | |-- libaio
| | |-- libidn
| | |-- libtirpc
| | |-- libuser
| | |-- libzypp
| | |-- lighttpd
| | |-- logrotate
| | |-- lsb
| | |-- lsof
| | |-- mailx
| | |-- man
| | |-- man-pages
| | |-- mc
| | |-- mdadm
| | |-- mingetty
| | |-- minicom
| | |-- mktemp
| | |-- msmtp
| | |-- nano
| | |-- net-tools
| | |-- newt
| | |-- nodejs
| | |-- pam
| | |-- parted
| | |-- pax
| | |-- perl
| | |-- polkit
| | |-- procps
| | |-- psmisc
| | |-- quota
| | |-- rpcbind
| | |-- sat-solver
| | |-- screen
| | |-- sed
| | |-- shadow
| | |-- slang
| | |-- sudo
| | |-- sysklogd
| | |-- sysstat
| | |-- tar
| | |-- tasks
| | |-- tcp-wrappers
| | |-- texinfo
| | |-- time
| | |-- tzcode
| | |-- tzdata
| | |-- unzip
| | |-- watchdog
| | |-- which
| | |-- xinetd
| | |-- xz
| | |-- zip
| | `-- zypper
| |-- recipes-gnome
| | |-- gdk-pixbuf
| | |-- gnome
| | |-- gthumb
| | |-- gtk+
| | |-- gtk-doc
| | |-- gtk-engines
| | |-- gtkhtml2
| | |-- gtk-theme-torturer
| | |-- hicolor-icon-theme
| | |-- libffi
| | |-- libglade
| | |-- libidl
| | |-- libnotify
| | |-- librsvg
| | |-- libsexy
| | |-- libunique
| | |-- ORBit2
| | `-- tasks
| |-- recipes-graphics
| | |-- cairo
| | |-- clutter
| | |-- directfb
| | |-- drm
| | |-- fontconfig
| | |-- freetype
| | |-- fstests
| | |-- glew
| | |-- images
| | |-- libfakekey
| | |-- libmatchbox
| | |-- libsdl
| | |-- libxsettings-client
| | |-- matchbox-session
| | |-- matchbox-wm
| | |-- matchbox-wm-2
| | |-- menu-cache
| | |-- mesa
| | |-- mutter
| | |-- notification-daemon
| | |-- pango
| | |-- rabbitmq
| | |-- startup-notification
| | |-- tasks
| | |-- tslib
| | |-- ttf-fonts
| | |-- x11-common
| | |-- x11vnc
| | |-- xcb
| | |-- xcursor-transparent-theme
| | |-- xorg-app
| | |-- xorg-driver
| | |-- xorg-font
| | |-- xorg-lib
| | |-- xorg-proto
| | |-- xorg-util
| | |-- xorg-xserver
| | |-- xrestop
| | |-- xtscal
| | `-- xvideo-tests
| |-- recipes-kernel
| | |-- blktrace
| | |-- dtc
| | |-- hello-mod
| | |-- kern-tools
| | |-- kexec
| | |-- latencytop
| | |-- linux
| | |-- linux-firmware
| | |-- linux-libc-headers
| | |-- lttng
| | |-- module-init-tools
| | |-- modutils
| | |-- oprofile
| | |-- powertop
| | |-- sysprof
| | |-- systemtap
| | |-- trace-cmd
| | `-- update-modules
| |-- recipes-multimedia
| | |-- alsa
| | |-- ccrtp
| | |-- commoncpp
| | |-- flac
| | |-- gstreamer
| | |-- lame
| | |-- liba52
| | |-- libid3tag
| | |-- libmad
| | |-- libogg
| | |-- libomxil
| | |-- libpng
| | |-- libsamplerate
| | |-- libsndfile
| | |-- libtheora
| | |-- libtiff
| | |-- libvorbis
| | |-- mpeg2dec
| | |-- musicbrainz
| | |-- ortp
| | |-- pulseaudio
| | |-- speex
| | `-- tremor
| |-- recipes-qt
| | |-- meta
| | |-- qt4
| | |-- qt-apps
| | `-- tasks
| |-- recipes-sato
| | |-- eds
| | |-- gaku
| | |-- gtk-engines
| | |-- images
| | |-- leafpad
| | |-- libical
| | |-- libowl
| | |-- matchbox-config-gtk
| | |-- matchbox-desktop
| | |-- matchbox-desktop-sato
| | |-- matchbox-keyboard
| | |-- matchbox-panel-2
| | |-- matchbox-sato
| | |-- matchbox-stroke
| | |-- matchbox-terminal
| | |-- matchbox-theme-sato
| | |-- owl-video-widget
| | |-- pcmanfm
| | |-- pimlico
| | |-- puzzles
| | |-- rxvt-unicode
| | |-- sato-icon-theme
| | |-- screenshot
| | |-- settings-daemon
| | |-- tasks
| | |-- web
| | `-- webkit
| |-- recipes-support
| | |-- apr
| | |-- aspell
| | |-- atk
| | |-- attr
| | |-- beecrypt
| | |-- boost
| | |-- consolekit
| | |-- createrepo
| | |-- curl
| | |-- cyrus-sasl
| | |-- db
| | |-- enchant
| | |-- gdbm
| | |-- gmp
| | |-- gnutls
| | |-- gpgme
| | |-- hal
| | |-- icu
| | |-- js
| | |-- krb
| | |-- libassuan
| | |-- libcap
| | |-- libcheck
| | |-- libcroco
| | |-- libdaemon
| | |-- libevent
| | |-- libexif
| | |-- libfm
| | |-- libgcrypt
| | |-- libgdbus
| | |-- libgpg-error
| | |-- libiconv
| | |-- libkeyutils
| | |-- libmpc
| | |-- libnl
| | |-- liboil
| | |-- libpcre
| | |-- libproxy
| | |-- libsoup
| | |-- liburcu
| | |-- libusb
| | |-- libxslt
| | |-- lzo
| | |-- mpfr
| | |-- neon
| | |-- openldap
| | |-- popt
| | |-- pth
| | |-- shared-mime-info
| | |-- sqlite
| | |-- taglib
| | `-- vte
| `-- site
|-- meta-demoapps
| |-- recipes-connectivity
| | |-- farsight
| | |-- libetpan
| | |-- loudmouth
| | |-- openswan
| | |-- opensync
| | |-- telepathy
| | `-- wbxml
| |-- recipes-gnome
| | |-- abiword
| | |-- gcalctool
| | |-- gnome
| | |-- libgsf
| | |-- libgtkstylus
| | `-- wv
| |-- recipes-graphics
| | |-- libxklavier
| | |-- pong-clock
| | |-- xorg-app
| | |-- xorg-lib
| | |-- xorg-proto
| | `-- xournal
| |-- recipes-kernel
| | `-- fuse
| |-- recipes-sato
| | |-- claws-mail
| | |-- clipboard-manager
| | |-- epdfview
| | |-- kf
| | |-- matchbox-themes-extra
| | `-- matchbox-themes-gtk
| `-- recipes-support
| |-- iso-codes
| |-- libfribidi
| |-- openobex
| `-- poppler
|-- meta-intel
| |-- common
| | |-- recipes-bsp
| | `-- recipes-core
| |-- meta-crownbay
| | |-- binary
| | |-- conf
| | |-- recipes-bsp
| | |-- recipes-graphics
| | `-- recipes-kernel
| |-- meta-emenlow
| | |-- binary
| | |-- conf
| | |-- recipes-bsp
| | |-- recipes-graphics
| | `-- recipes-kernel
| |-- meta-fishriver
| | |-- binary
| | |-- conf
| | |-- recipes-bsp
| | |-- recipes-graphics
| | `-- recipes-kernel
| |-- meta-jasperforest
| | |-- binary
| | |-- conf
| | |-- recipes-bsp
| | |-- recipes-graphics
| | `-- recipes-kernel
| |-- meta-n450
| | |-- conf
| | |-- docs
| | |-- recipes-bsp
| | |-- recipes-graphics
| | `-- recipes-kernel
| `-- meta-sugarbay
| |-- binary
| |-- conf
| |-- recipes-bsp
| |-- recipes-graphics
| `-- recipes-kernel
|-- meta-rt
| |-- conf
| |-- images
| |-- recipes-kernel
| `-- recipes-tests
`-- scripts
|-- contrib
| `-- python
|-- jhbuild
| `-- modulesets
`-- qemuimage-tests
|-- sanity
|-- scenario
`-- tools
581 directories
[-- Attachment #3: modify_poky_tree.log --]
[-- Type: text/x-log, Size: 40150 bytes --]
.
├── arch
│ ├── alpha
│ │ ├── boot
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ └── oprofile
│ ├── arm
│ │ ├── boot
│ │ ├── common
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mach-aaec2000
│ │ ├── mach-at91
│ │ ├── mach-bcmring
│ │ ├── mach-clps711x
│ │ ├── mach-cns3xxx
│ │ ├── mach-davinci
│ │ ├── mach-dove
│ │ ├── mach-ebsa110
│ │ ├── mach-ep93xx
│ │ ├── mach-footbridge
│ │ ├── mach-gemini
│ │ ├── mach-h720x
│ │ ├── mach-imx
│ │ ├── mach-integrator
│ │ ├── mach-iop13xx
│ │ ├── mach-iop32x
│ │ ├── mach-iop33x
│ │ ├── mach-ixp2000
│ │ ├── mach-ixp23xx
│ │ ├── mach-ixp4xx
│ │ ├── mach-kirkwood
│ │ ├── mach-ks8695
│ │ ├── mach-l7200
│ │ ├── mach-lh7a40x
│ │ ├── mach-loki
│ │ ├── mach-lpc32xx
│ │ ├── mach-mmp
│ │ ├── mach-msm
│ │ ├── mach-mv78xx0
│ │ ├── mach-mx25
│ │ ├── mach-mx3
│ │ ├── mach-mx5
│ │ ├── mach-mxc91231
│ │ ├── mach-netx
│ │ ├── mach-nomadik
│ │ ├── mach-ns9xxx
│ │ ├── mach-nuc93x
│ │ ├── mach-omap1
│ │ ├── mach-omap2
│ │ ├── mach-orion5x
│ │ ├── mach-pnx4008
│ │ ├── mach-pxa
│ │ ├── mach-realview
│ │ ├── mach-rpc
│ │ ├── mach-s3c2400
│ │ ├── mach-s3c2410
│ │ ├── mach-s3c2412
│ │ ├── mach-s3c2416
│ │ ├── mach-s3c2440
│ │ ├── mach-s3c2443
│ │ ├── mach-s3c24a0
│ │ ├── mach-s3c64xx
│ │ ├── mach-s5p6442
│ │ ├── mach-s5p64x0
│ │ ├── mach-s5pc100
│ │ ├── mach-s5pv210
│ │ ├── mach-s5pv310
│ │ ├── mach-sa1100
│ │ ├── mach-shark
│ │ ├── mach-shmobile
│ │ ├── mach-spear3xx
│ │ ├── mach-spear6xx
│ │ ├── mach-stmp378x
│ │ ├── mach-stmp37xx
│ │ ├── mach-tcc8k
│ │ ├── mach-tegra
│ │ ├── mach-u300
│ │ ├── mach-ux500
│ │ ├── mach-versatile
│ │ ├── mach-vexpress
│ │ ├── mach-w90x900
│ │ ├── mm
│ │ ├── nwfpe
│ │ ├── oprofile
│ │ ├── plat-iop
│ │ ├── plat-mxc
│ │ ├── plat-nomadik
│ │ ├── plat-omap
│ │ ├── plat-orion
│ │ ├── plat-pxa
│ │ ├── plat-s3c24xx
│ │ ├── plat-s5p
│ │ ├── plat-samsung
│ │ ├── plat-spear
│ │ ├── plat-stmp3xxx
│ │ ├── plat-tcc
│ │ ├── plat-versatile
│ │ ├── tools
│ │ └── vfp
│ ├── avr32
│ │ ├── boards
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mach-at32ap
│ │ ├── mm
│ │ └── oprofile
│ ├── blackfin
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mach-bf518
│ │ ├── mach-bf527
│ │ ├── mach-bf533
│ │ ├── mach-bf537
│ │ ├── mach-bf538
│ │ ├── mach-bf548
│ │ ├── mach-bf561
│ │ ├── mach-common
│ │ ├── mm
│ │ └── oprofile
│ ├── cris
│ │ ├── arch-v10
│ │ ├── arch-v32
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ └── mm
│ ├── frv
│ │ ├── boot
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mb93090-mb00
│ │ └── mm
│ ├── h8300
│ │ ├── boot
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mm
│ │ └── platform
│ ├── ia64
│ │ ├── configs
│ │ ├── dig
│ │ ├── hp
│ │ ├── include
│ │ ├── kernel
│ │ ├── kvm
│ │ ├── lib
│ │ ├── mm
│ │ ├── oprofile
│ │ ├── pci
│ │ ├── scripts
│ │ ├── sn
│ │ ├── uv
│ │ └── xen
│ ├── m32r
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mm
│ │ ├── oprofile
│ │ └── platforms
│ ├── m68k
│ │ ├── amiga
│ │ ├── apollo
│ │ ├── atari
│ │ ├── bvme6000
│ │ ├── configs
│ │ ├── fpsp040
│ │ ├── hp300
│ │ ├── ifpsp060
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mac
│ │ ├── math-emu
│ │ ├── mm
│ │ ├── mvme147
│ │ ├── mvme16x
│ │ ├── q40
│ │ ├── sun3
│ │ ├── sun3x
│ │ └── tools
│ ├── m68knommu
│ │ ├── configs
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mm
│ │ └── platform
│ ├── microblaze
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mm
│ │ ├── oprofile
│ │ ├── pci
│ │ └── platform
│ ├── mips
│ │ ├── alchemy
│ │ ├── ar7
│ │ ├── bcm47xx
│ │ ├── bcm63xx
│ │ ├── boot
│ │ ├── cavium-octeon
│ │ ├── cobalt
│ │ ├── configs
│ │ ├── dec
│ │ ├── emma
│ │ ├── fw
│ │ ├── include
│ │ ├── jazz
│ │ ├── jz4740
│ │ ├── kernel
│ │ ├── lasat
│ │ ├── lib
│ │ ├── loongson
│ │ ├── math-emu
│ │ ├── mipssim
│ │ ├── mm
│ │ ├── mti-malta
│ │ ├── nxp
│ │ ├── oprofile
│ │ ├── pci
│ │ ├── pmc-sierra
│ │ ├── pnx833x
│ │ ├── pnx8550
│ │ ├── power
│ │ ├── powertv
│ │ ├── rb532
│ │ ├── sgi-ip22
│ │ ├── sgi-ip27
│ │ ├── sgi-ip32
│ │ ├── sibyte
│ │ ├── sni
│ │ ├── txx9
│ │ ├── vr41xx
│ │ └── wrppmc
│ ├── mn10300
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── mm
│ │ ├── oprofile
│ │ ├── proc-mn103e010
│ │ ├── proc-mn2ws0050
│ │ ├── unit-asb2303
│ │ ├── unit-asb2305
│ │ └── unit-asb2364
│ ├── parisc
│ │ ├── configs
│ │ ├── hpux
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ └── oprofile
│ ├── powerpc
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── kvm
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ ├── oprofile
│ │ ├── platforms
│ │ ├── sysdev
│ │ └── xmon
│ ├── s390
│ │ ├── appldata
│ │ ├── boot
│ │ ├── crypto
│ │ ├── hypfs
│ │ ├── include
│ │ ├── kernel
│ │ ├── kvm
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ └── oprofile
│ ├── score
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ └── mm
│ ├── sh
│ │ ├── boards
│ │ ├── boot
│ │ ├── cchips
│ │ ├── configs
│ │ ├── drivers
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── lib64
│ │ ├── math-emu
│ │ ├── mm
│ │ ├── oprofile
│ │ └── tools
│ ├── sparc
│ │ ├── boot
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ ├── oprofile
│ │ └── prom
│ ├── tile
│ │ ├── configs
│ │ ├── include
│ │ ├── kernel
│ │ ├── kvm
│ │ ├── lib
│ │ └── mm
│ ├── um
│ │ ├── drivers
│ │ ├── include
│ │ ├── kernel
│ │ ├── os-Linux
│ │ ├── scripts
│ │ ├── sys-i386
│ │ ├── sys-ia64
│ │ ├── sys-ppc
│ │ └── sys-x86_64
│ ├── x86
│ │ ├── boot
│ │ ├── configs
│ │ ├── crypto
│ │ ├── ia32
│ │ ├── include
│ │ ├── kernel
│ │ ├── kvm
│ │ ├── lguest
│ │ ├── lib
│ │ ├── math-emu
│ │ ├── mm
│ │ ├── oprofile
│ │ ├── pci
│ │ ├── platform
│ │ ├── power
│ │ ├── tools
│ │ ├── vdso
│ │ ├── video
│ │ └── xen
│ └── xtensa
│ ├── boot
│ ├── configs
│ ├── include
│ ├── kernel
│ ├── lib
│ ├── mm
│ ├── platforms
│ └── variants
├── bitbake
│ └── lib
│ ├── bb
│ └── ply
├── block
├── build
│ ├── conf
│ ├── downloads
│ │ └── git2
│ ├── sstate-cache
│ └── tmp
│ ├── buildstats
│ ├── cache
│ ├── sstate-control
│ ├── stamps
│ ├── sysroots
│ └── work
├── crypto
│ └── async_tx
├── Documentation
│ ├── ABI
│ │ ├── obsolete
│ │ ├── removed
│ │ ├── stable
│ │ └── testing
│ ├── accounting
│ ├── acpi
│ │ └── apei
│ ├── aoe
│ ├── arm
│ │ ├── msm
│ │ ├── nwfpe
│ │ ├── OMAP
│ │ ├── pxa
│ │ ├── SA1100
│ │ ├── Samsung
│ │ ├── Samsung-S3C24XX
│ │ ├── Sharp-LH
│ │ ├── SPEAr
│ │ └── VFP
│ ├── auxdisplay
│ ├── blackfin
│ ├── block
│ ├── blockdev
│ │ └── drbd
│ ├── cdrom
│ ├── cgroups
│ ├── connector
│ ├── console
│ ├── cpu-freq
│ ├── cpuidle
│ ├── cris
│ ├── crypto
│ ├── development-process
│ ├── device-mapper
│ ├── DocBook
│ │ ├── dvb
│ │ └── v4l
│ ├── driver-model
│ ├── dvb
│ ├── early-userspace
│ ├── fault-injection
│ ├── fb
│ ├── filesystems
│ │ ├── caching
│ │ ├── configfs
│ │ ├── nfs
│ │ └── pohmelfs
│ ├── firmware_class
│ ├── frv
│ ├── hwmon
│ ├── i2c
│ │ └── busses
│ ├── i2o
│ ├── ia64
│ ├── ide
│ ├── infiniband
│ ├── input
│ ├── ioctl
│ ├── isdn
│ ├── ja_JP
│ ├── kbuild
│ ├── kdump
│ ├── ko_KR
│ ├── kvm
│ ├── laptops
│ ├── leds
│ ├── lguest
│ ├── m68k
│ ├── make
│ ├── mips
│ ├── misc-devices
│ ├── mmc
│ ├── mn10300
│ ├── mtd
│ ├── namespaces
│ ├── netlabel
│ ├── networking
│ │ ├── caif
│ │ ├── mac80211_hwsim
│ │ └── timestamping
│ ├── parisc
│ ├── PCI
│ ├── pcmcia
│ ├── power
│ │ └── regulator
│ ├── powerpc
│ │ └── dts-bindings
│ ├── pps
│ ├── prctl
│ ├── RCU
│ ├── s390
│ ├── scheduler
│ ├── scsi
│ ├── serial
│ ├── sh
│ ├── sound
│ │ ├── alsa
│ │ └── oss
│ ├── sparc
│ ├── spi
│ ├── sysctl
│ ├── telephony
│ ├── thermal
│ ├── timers
│ ├── trace
│ │ └── postprocess
│ ├── uml
│ ├── usb
│ ├── video4linux
│ │ ├── bttv
│ │ ├── cx2341x
│ │ └── cx88
│ ├── vm
│ ├── w1
│ │ ├── masters
│ │ └── slaves
│ ├── watchdog
│ │ └── src
│ ├── wimax
│ ├── x86
│ │ ├── i386
│ │ └── x86_64
│ └── zh_CN
├── drivers
│ ├── accessibility
│ │ └── braille
│ ├── acpi
│ │ ├── acpica
│ │ └── apei
│ ├── amba
│ ├── ata
│ ├── atm
│ ├── auxdisplay
│ ├── base
│ │ └── power
│ ├── block
│ │ ├── aoe
│ │ ├── drbd
│ │ └── paride
│ ├── bluetooth
│ ├── cbus
│ ├── cdrom
│ ├── char
│ │ ├── agp
│ │ ├── hw_random
│ │ ├── ip2
│ │ ├── ipmi
│ │ ├── mwave
│ │ ├── pcmcia
│ │ ├── rio
│ │ ├── tpm
│ │ └── xilinx_hwicap
│ ├── clocksource
│ ├── connector
│ ├── cpufreq
│ ├── cpuidle
│ │ └── governors
│ ├── crypto
│ │ └── amcc
│ ├── dca
│ ├── dio
│ ├── dma
│ │ ├── ioat
│ │ ├── ipu
│ │ └── ppc4xx
│ ├── edac
│ ├── eisa
│ ├── firewire
│ ├── firmware
│ ├── gpio
│ ├── gpu
│ │ ├── drm
│ │ ├── stub
│ │ └── vga
│ ├── hid
│ │ └── usbhid
│ ├── hwmon
│ ├── i2c
│ │ ├── algos
│ │ ├── busses
│ │ └── muxes
│ ├── ide
│ ├── idle
│ ├── ieee802154
│ ├── infiniband
│ │ ├── core
│ │ ├── hw
│ │ └── ulp
│ ├── input
│ │ ├── gameport
│ │ ├── joystick
│ │ ├── keyboard
│ │ ├── misc
│ │ ├── mouse
│ │ ├── serio
│ │ ├── tablet
│ │ └── touchscreen
│ ├── isdn
│ │ ├── act2000
│ │ ├── capi
│ │ ├── divert
│ │ ├── gigaset
│ │ ├── hardware
│ │ ├── hisax
│ │ ├── hysdn
│ │ ├── i4l
│ │ ├── icn
│ │ ├── isdnloop
│ │ ├── mISDN
│ │ ├── pcbit
│ │ └── sc
│ ├── leds
│ ├── lguest
│ │ └── x86
│ ├── macintosh
│ │ └── ams
│ ├── mca
│ ├── md
│ ├── media
│ │ ├── common
│ │ ├── dvb
│ │ ├── IR
│ │ ├── radio
│ │ └── video
│ ├── memstick
│ │ ├── core
│ │ └── host
│ ├── message
│ │ ├── fusion
│ │ └── i2o
│ ├── mfd
│ ├── misc
│ │ ├── c2port
│ │ ├── cb710
│ │ ├── eeprom
│ │ ├── ibmasm
│ │ ├── iwmc3200top
│ │ ├── sgi-gru
│ │ ├── sgi-xp
│ │ └── ti-st
│ ├── mmc
│ │ ├── card
│ │ ├── core
│ │ └── host
│ ├── mtd
│ │ ├── chips
│ │ ├── devices
│ │ ├── lpddr
│ │ ├── maps
│ │ ├── nand
│ │ ├── onenand
│ │ ├── tests
│ │ └── ubi
│ ├── net
│ │ ├── appletalk
│ │ ├── arcnet
│ │ ├── arm
│ │ ├── atl1c
│ │ ├── atl1e
│ │ ├── atlx
│ │ ├── benet
│ │ ├── bna
│ │ ├── bnx2x
│ │ ├── bonding
│ │ ├── caif
│ │ ├── can
│ │ ├── chelsio
│ │ ├── cris
│ │ ├── cxgb3
│ │ ├── cxgb4
│ │ ├── cxgb4vf
│ │ ├── e1000
│ │ ├── e1000e
│ │ ├── ehea
│ │ ├── enic
│ │ ├── fs_enet
│ │ ├── hamradio
│ │ ├── ibm_newemac
│ │ ├── igb
│ │ ├── igbvf
│ │ ├── irda
│ │ ├── ixgb
│ │ ├── ixgbe
│ │ ├── ixgbevf
│ │ ├── ixp2000
│ │ ├── mlx4
│ │ ├── myri10ge
│ │ ├── netxen
│ │ ├── octeon
│ │ ├── pch_gbe
│ │ ├── pcmcia
│ │ ├── phy
│ │ ├── qlcnic
│ │ ├── qlge
│ │ ├── sfc
│ │ ├── skfp
│ │ ├── stmmac
│ │ ├── tile
│ │ ├── tokenring
│ │ ├── tulip
│ │ ├── usb
│ │ ├── vmxnet3
│ │ ├── vxge
│ │ ├── wan
│ │ ├── wimax
│ │ └── wireless
│ ├── nubus
│ ├── of
│ ├── oprofile
│ ├── parisc
│ ├── parport
│ ├── pci
│ │ ├── hotplug
│ │ └── pcie
│ ├── pcmcia
│ ├── platform
│ │ └── x86
│ ├── pnp
│ │ ├── isapnp
│ │ ├── pnpacpi
│ │ └── pnpbios
│ ├── power
│ ├── pps
│ │ └── clients
│ ├── ps3
│ ├── rapidio
│ │ └── switches
│ ├── regulator
│ ├── rtc
│ ├── s390
│ │ ├── block
│ │ ├── char
│ │ ├── cio
│ │ ├── crypto
│ │ ├── kvm
│ │ ├── net
│ │ └── scsi
│ ├── sbus
│ │ └── char
│ ├── scsi
│ │ ├── aacraid
│ │ ├── aic7xxx
│ │ ├── aic7xxx_old
│ │ ├── aic94xx
│ │ ├── arcmsr
│ │ ├── arm
│ │ ├── be2iscsi
│ │ ├── bfa
│ │ ├── bnx2i
│ │ ├── cxgbi
│ │ ├── device_handler
│ │ ├── dpt
│ │ ├── fcoe
│ │ ├── fnic
│ │ ├── ibmvscsi
│ │ ├── libfc
│ │ ├── libsas
│ │ ├── lpfc
│ │ ├── megaraid
│ │ ├── mpt2sas
│ │ ├── mvsas
│ │ ├── osd
│ │ ├── pcmcia
│ │ ├── pm8001
│ │ ├── qla2xxx
│ │ ├── qla4xxx
│ │ └── sym53c8xx_2
│ ├── serial
│ │ ├── cpm_uart
│ │ └── jsm
│ ├── sfi
│ ├── sh
│ │ ├── clk
│ │ ├── intc
│ │ ├── maple
│ │ └── superhyway
│ ├── sn
│ ├── spi
│ ├── ssb
│ ├── staging
│ │ ├── adis16255
│ │ ├── asus_oled
│ │ ├── ath6kl
│ │ ├── autofs
│ │ ├── batman-adv
│ │ ├── bcm
│ │ ├── brcm80211
│ │ ├── comedi
│ │ ├── cpia
│ │ ├── crystalhd
│ │ ├── cx25821
│ │ ├── cxt1e1
│ │ ├── dt3155v4l
│ │ ├── easycap
│ │ ├── echo
│ │ ├── et131x
│ │ ├── frontier
│ │ ├── ft1000
│ │ ├── go7007
│ │ ├── hv
│ │ ├── iio
│ │ ├── intel_sst
│ │ ├── keucr
│ │ ├── line6
│ │ ├── lirc
│ │ ├── memrar
│ │ ├── msm
│ │ ├── octeon
│ │ ├── olpc_dcon
│ │ ├── panel
│ │ ├── phison
│ │ ├── pohmelfs
│ │ ├── quatech_usb2
│ │ ├── quickstart
│ │ ├── rt2860
│ │ ├── rt2870
│ │ ├── rtl8187se
│ │ ├── rtl8192e
│ │ ├── rtl8192u
│ │ ├── rtl8712
│ │ ├── samsung-laptop
│ │ ├── sbe-2t3e3
│ │ ├── serqt_usb2
│ │ ├── slicoss
│ │ ├── sm7xx
│ │ ├── smbfs
│ │ ├── solo6x10
│ │ ├── speakup
│ │ ├── spectra
│ │ ├── stradis
│ │ ├── tidspbridge
│ │ ├── ti-st
│ │ ├── tm6000
│ │ ├── udlfb
│ │ ├── usbip
│ │ ├── vme
│ │ ├── vt6655
│ │ ├── vt6656
│ │ ├── westbridge
│ │ ├── winbond
│ │ ├── wlags49_h2
│ │ ├── wlags49_h25
│ │ ├── wlan-ng
│ │ ├── xgifb
│ │ └── zram
│ ├── tc
│ ├── telephony
│ ├── thermal
│ ├── tty
│ │ └── vt
│ ├── uio
│ ├── usb
│ │ ├── atm
│ │ ├── c67x00
│ │ ├── class
│ │ ├── core
│ │ ├── early
│ │ ├── gadget
│ │ ├── host
│ │ ├── image
│ │ ├── misc
│ │ ├── mon
│ │ ├── musb
│ │ ├── otg
│ │ ├── serial
│ │ ├── storage
│ │ └── wusbcore
│ ├── uwb
│ │ └── i1480
│ ├── vhost
│ ├── video
│ │ ├── aty
│ │ ├── backlight
│ │ ├── console
│ │ ├── display
│ │ ├── geode
│ │ ├── i810
│ │ ├── intelfb
│ │ ├── kyro
│ │ ├── logo
│ │ ├── matrox
│ │ ├── mb862xx
│ │ ├── mbx
│ │ ├── msm
│ │ ├── nvidia
│ │ ├── omap
│ │ ├── omap2
│ │ ├── pnx4008
│ │ ├── riva
│ │ ├── savage
│ │ ├── sis
│ │ ├── vermilion
│ │ └── via
│ ├── virtio
│ ├── vlynq
│ ├── w1
│ │ ├── masters
│ │ └── slaves
│ ├── watchdog
│ ├── xen
│ │ ├── xenbus
│ │ └── xenfs
│ └── zorro
├── firmware
│ ├── 3com
│ ├── acenic
│ ├── adaptec
│ ├── advansys
│ ├── av7110
│ ├── bnx2
│ ├── bnx2x
│ ├── cis
│ ├── cpia2
│ ├── cxgb3
│ ├── dabusb
│ ├── dsp56k
│ ├── e100
│ ├── edgeport
│ ├── emi26
│ ├── emi62
│ ├── ess
│ ├── kaweth
│ ├── keyspan
│ ├── keyspan_pda
│ ├── korg
│ ├── matrox
│ ├── myricom
│ ├── ositech
│ ├── qlogic
│ ├── r128
│ ├── radeon
│ ├── sb16
│ ├── sun
│ ├── tehuti
│ ├── tigon
│ ├── ttusb-budget
│ ├── vicam
│ ├── yam
│ └── yamaha
├── fs
│ ├── 9p
│ ├── adfs
│ ├── affs
│ ├── afs
│ ├── autofs4
│ ├── befs
│ ├── bfs
│ ├── btrfs
│ ├── cachefiles
│ ├── ceph
│ ├── cifs
│ ├── coda
│ ├── configfs
│ ├── cramfs
│ ├── debugfs
│ ├── devpts
│ ├── dlm
│ ├── ecryptfs
│ ├── efs
│ ├── exofs
│ ├── exportfs
│ ├── ext2
│ ├── ext3
│ ├── ext4
│ ├── fat
│ ├── freevxfs
│ ├── fscache
│ ├── fuse
│ ├── gfs2
│ ├── hfs
│ ├── hfsplus
│ ├── hostfs
│ ├── hpfs
│ ├── hppfs
│ ├── hugetlbfs
│ ├── isofs
│ ├── jbd
│ ├── jbd2
│ ├── jffs2
│ ├── jfs
│ ├── lockd
│ ├── logfs
│ ├── minix
│ ├── ncpfs
│ ├── nfs
│ ├── nfs_common
│ ├── nfsd
│ ├── nilfs2
│ ├── nls
│ ├── notify
│ │ ├── dnotify
│ │ ├── fanotify
│ │ └── inotify
│ ├── ntfs
│ ├── ocfs2
│ │ ├── cluster
│ │ ├── dlm
│ │ └── dlmfs
│ ├── omfs
│ ├── openpromfs
│ ├── partitions
│ ├── proc
│ ├── qnx4
│ ├── quota
│ ├── ramfs
│ ├── reiserfs
│ ├── romfs
│ ├── squashfs
│ ├── sysfs
│ ├── sysv
│ ├── ubifs
│ ├── udf
│ ├── ufs
│ └── xfs
│ ├── linux-2.6
│ ├── quota
│ └── support
├── include
│ ├── acpi
│ │ └── platform
│ ├── asm-generic
│ │ └── bitops
│ ├── crypto
│ │ └── internal
│ ├── drm
│ │ ├── i2c
│ │ └── ttm
│ ├── keys
│ ├── linux
│ │ ├── amba
│ │ ├── byteorder
│ │ ├── caif
│ │ ├── can
│ │ ├── ceph
│ │ ├── crush
│ │ ├── decompress
│ │ ├── dvb
│ │ ├── hdlc
│ │ ├── i2c
│ │ ├── input
│ │ ├── isdn
│ │ ├── lockd
│ │ ├── mfd
│ │ ├── mlx4
│ │ ├── mmc
│ │ ├── mtd
│ │ ├── netfilter
│ │ ├── netfilter_arp
│ │ ├── netfilter_bridge
│ │ ├── netfilter_ipv4
│ │ ├── netfilter_ipv6
│ │ ├── nfsd
│ │ ├── power
│ │ ├── raid
│ │ ├── regulator
│ │ ├── rtc
│ │ ├── spi
│ │ ├── ssb
│ │ ├── sunrpc
│ │ ├── tc_act
│ │ ├── tc_ematch
│ │ ├── unaligned
│ │ ├── usb
│ │ ├── uwb
│ │ └── wimax
│ ├── math-emu
│ ├── media
│ │ └── davinci
│ ├── mtd
│ ├── net
│ │ ├── 9p
│ │ ├── bluetooth
│ │ ├── caif
│ │ ├── irda
│ │ ├── iucv
│ │ ├── netfilter
│ │ ├── netns
│ │ ├── phonet
│ │ ├── sctp
│ │ ├── tc_act
│ │ └── tipc
│ ├── pcmcia
│ ├── rdma
│ ├── rxrpc
│ ├── scsi
│ │ └── fc
│ ├── sound
│ ├── trace
│ │ └── events
│ ├── video
│ └── xen
│ └── interface
├── init
├── ipc
├── kernel
│ ├── debug
│ │ └── kdb
│ ├── gcov
│ ├── irq
│ ├── power
│ ├── time
│ └── trace
├── lib
│ ├── lzo
│ ├── raid6
│ │ └── test
│ ├── reed_solomon
│ ├── zlib_deflate
│ └── zlib_inflate
├── meta
│ ├── conf
│ │ └── distro
│ ├── lib
│ │ └── oe
│ ├── recipes-core
│ │ ├── images
│ │ └── notification-daemon
│ ├── recipes-gnome
│ │ └── gdk-pixbuf
│ ├── recipes-graphics
│ │ ├── drm
│ │ └── mesa
│ └── recipes-kernel
│ └── linux
├── mm
├── net
│ ├── 802
│ ├── 8021q
│ ├── 9p
│ ├── appletalk
│ ├── atm
│ ├── ax25
│ ├── bluetooth
│ │ ├── bnep
│ │ ├── cmtp
│ │ ├── hidp
│ │ └── rfcomm
│ ├── bridge
│ │ └── netfilter
│ ├── caif
│ ├── can
│ ├── ceph
│ │ └── crush
│ ├── core
│ ├── dcb
│ ├── dccp
│ │ └── ccids
│ ├── decnet
│ │ └── netfilter
│ ├── dns_resolver
│ ├── dsa
│ ├── econet
│ ├── ethernet
│ ├── ieee802154
│ ├── ipv4
│ │ └── netfilter
│ ├── ipv6
│ │ └── netfilter
│ ├── ipx
│ ├── irda
│ │ ├── ircomm
│ │ ├── irlan
│ │ └── irnet
│ ├── iucv
│ ├── key
│ ├── l2tp
│ ├── lapb
│ ├── llc
│ ├── mac80211
│ ├── netfilter
│ │ └── ipvs
│ ├── netlabel
│ ├── netlink
│ ├── netrom
│ ├── packet
│ ├── phonet
│ ├── rds
│ ├── rfkill
│ ├── rose
│ ├── rxrpc
│ ├── sched
│ ├── sctp
│ ├── sunrpc
│ │ ├── auth_gss
│ │ └── xprtrdma
│ ├── tipc
│ ├── unix
│ ├── wanrouter
│ ├── wimax
│ ├── wireless
│ ├── x25
│ └── xfrm
├── samples
│ ├── hw_breakpoint
│ ├── kdb
│ ├── kfifo
│ ├── kobject
│ ├── kprobes
│ ├── markers
│ ├── trace_events
│ └── tracepoints
├── scripts
│ ├── basic
│ ├── coccinelle
│ │ ├── api
│ │ ├── free
│ │ ├── iterators
│ │ ├── locks
│ │ ├── misc
│ │ ├── null
│ │ └── tests
│ ├── dtc
│ │ └── libfdt
│ ├── genksyms
│ ├── kconfig
│ │ └── lxdialog
│ ├── ksymoops
│ ├── mod
│ ├── package
│ ├── rt-tester
│ ├── selinux
│ │ ├── genheaders
│ │ └── mdp
│ └── tracing
├── security
│ ├── apparmor
│ │ └── include
│ ├── integrity
│ │ └── ima
│ ├── keys
│ ├── selinux
│ │ ├── include
│ │ └── ss
│ ├── smack
│ └── tomoyo
├── sound
│ ├── aoa
│ │ ├── codecs
│ │ ├── core
│ │ ├── fabrics
│ │ └── soundbus
│ ├── arm
│ ├── atmel
│ ├── core
│ │ ├── oss
│ │ └── seq
│ ├── drivers
│ │ ├── mpu401
│ │ ├── opl3
│ │ ├── opl4
│ │ ├── pcsp
│ │ └── vx
│ ├── i2c
│ │ └── other
│ ├── isa
│ │ ├── ad1816a
│ │ ├── ad1848
│ │ ├── cs423x
│ │ ├── es1688
│ │ ├── galaxy
│ │ ├── gus
│ │ ├── msnd
│ │ ├── opti9xx
│ │ ├── sb
│ │ ├── wavefront
│ │ └── wss
│ ├── mips
│ ├── oss
│ │ └── dmasound
│ ├── parisc
│ ├── pci
│ │ ├── ac97
│ │ ├── ali5451
│ │ ├── asihpi
│ │ ├── au88x0
│ │ ├── aw2
│ │ ├── ca0106
│ │ ├── cs46xx
│ │ ├── cs5535audio
│ │ ├── ctxfi
│ │ ├── echoaudio
│ │ ├── emu10k1
│ │ ├── hda
│ │ ├── ice1712
│ │ ├── korg1212
│ │ ├── lx6464es
│ │ ├── mixart
│ │ ├── nm256
│ │ ├── oxygen
│ │ ├── pcxhr
│ │ ├── riptide
│ │ ├── rme9652
│ │ ├── trident
│ │ ├── vx222
│ │ └── ymfpci
│ ├── pcmcia
│ │ ├── pdaudiocf
│ │ └── vx
│ ├── ppc
│ ├── sh
│ ├── soc
│ │ ├── atmel
│ │ ├── au1x
│ │ ├── blackfin
│ │ ├── codecs
│ │ ├── davinci
│ │ ├── ep93xx
│ │ ├── fsl
│ │ ├── imx
│ │ ├── jz4740
│ │ ├── kirkwood
│ │ ├── nuc900
│ │ ├── omap
│ │ ├── pxa
│ │ ├── s3c24xx
│ │ ├── s6000
│ │ ├── sh
│ │ └── txx9
│ ├── sparc
│ ├── spi
│ ├── synth
│ │ └── emux
│ └── usb
│ ├── caiaq
│ ├── misc
│ └── usx2y
├── tools
│ ├── firewire
│ ├── perf
│ │ ├── arch
│ │ ├── bench
│ │ ├── Documentation
│ │ ├── scripts
│ │ └── util
│ └── usb
├── usr
└── virt
└── kvm
1337 directories
[-- Attachment #4: modify_poky_tree_level2.log --]
[-- Type: text/x-log, Size: 11163 bytes --]
.
├── arch
│ ├── alpha
│ ├── arm
│ ├── avr32
│ ├── blackfin
│ ├── cris
│ ├── frv
│ ├── h8300
│ ├── ia64
│ ├── m32r
│ ├── m68k
│ ├── m68knommu
│ ├── microblaze
│ ├── mips
│ ├── mn10300
│ ├── parisc
│ ├── powerpc
│ ├── s390
│ ├── score
│ ├── sh
│ ├── sparc
│ ├── tile
│ ├── um
│ ├── x86
│ └── xtensa
├── bitbake
│ └── lib
├── block
├── build
│ ├── conf
│ ├── downloads
│ ├── sstate-cache
│ └── tmp
├── crypto
│ └── async_tx
├── Documentation
│ ├── ABI
│ ├── accounting
│ ├── acpi
│ ├── aoe
│ ├── arm
│ ├── auxdisplay
│ ├── blackfin
│ ├── block
│ ├── blockdev
│ ├── cdrom
│ ├── cgroups
│ ├── connector
│ ├── console
│ ├── cpu-freq
│ ├── cpuidle
│ ├── cris
│ ├── crypto
│ ├── development-process
│ ├── device-mapper
│ ├── DocBook
│ ├── driver-model
│ ├── dvb
│ ├── early-userspace
│ ├── fault-injection
│ ├── fb
│ ├── filesystems
│ ├── firmware_class
│ ├── frv
│ ├── hwmon
│ ├── i2c
│ ├── i2o
│ ├── ia64
│ ├── ide
│ ├── infiniband
│ ├── input
│ ├── ioctl
│ ├── isdn
│ ├── ja_JP
│ ├── kbuild
│ ├── kdump
│ ├── ko_KR
│ ├── kvm
│ ├── laptops
│ ├── leds
│ ├── lguest
│ ├── m68k
│ ├── make
│ ├── mips
│ ├── misc-devices
│ ├── mmc
│ ├── mn10300
│ ├── mtd
│ ├── namespaces
│ ├── netlabel
│ ├── networking
│ ├── parisc
│ ├── PCI
│ ├── pcmcia
│ ├── power
│ ├── powerpc
│ ├── pps
│ ├── prctl
│ ├── RCU
│ ├── s390
│ ├── scheduler
│ ├── scsi
│ ├── serial
│ ├── sh
│ ├── sound
│ ├── sparc
│ ├── spi
│ ├── sysctl
│ ├── telephony
│ ├── thermal
│ ├── timers
│ ├── trace
│ ├── uml
│ ├── usb
│ ├── video4linux
│ ├── vm
│ ├── w1
│ ├── watchdog
│ ├── wimax
│ ├── x86
│ └── zh_CN
├── drivers
│ ├── accessibility
│ ├── acpi
│ ├── amba
│ ├── ata
│ ├── atm
│ ├── auxdisplay
│ ├── base
│ ├── block
│ ├── bluetooth
│ ├── cbus
│ ├── cdrom
│ ├── char
│ ├── clocksource
│ ├── connector
│ ├── cpufreq
│ ├── cpuidle
│ ├── crypto
│ ├── dca
│ ├── dio
│ ├── dma
│ ├── edac
│ ├── eisa
│ ├── firewire
│ ├── firmware
│ ├── gpio
│ ├── gpu
│ ├── hid
│ ├── hwmon
│ ├── i2c
│ ├── ide
│ ├── idle
│ ├── ieee802154
│ ├── infiniband
│ ├── input
│ ├── isdn
│ ├── leds
│ ├── lguest
│ ├── macintosh
│ ├── mca
│ ├── md
│ ├── media
│ ├── memstick
│ ├── message
│ ├── mfd
│ ├── misc
│ ├── mmc
│ ├── mtd
│ ├── net
│ ├── nubus
│ ├── of
│ ├── oprofile
│ ├── parisc
│ ├── parport
│ ├── pci
│ ├── pcmcia
│ ├── platform
│ ├── pnp
│ ├── power
│ ├── pps
│ ├── ps3
│ ├── rapidio
│ ├── regulator
│ ├── rtc
│ ├── s390
│ ├── sbus
│ ├── scsi
│ ├── serial
│ ├── sfi
│ ├── sh
│ ├── sn
│ ├── spi
│ ├── ssb
│ ├── staging
│ ├── tc
│ ├── telephony
│ ├── thermal
│ ├── tty
│ ├── uio
│ ├── usb
│ ├── uwb
│ ├── vhost
│ ├── video
│ ├── virtio
│ ├── vlynq
│ ├── w1
│ ├── watchdog
│ ├── xen
│ └── zorro
├── firmware
│ ├── 3com
│ ├── acenic
│ ├── adaptec
│ ├── advansys
│ ├── av7110
│ ├── bnx2
│ ├── bnx2x
│ ├── cis
│ ├── cpia2
│ ├── cxgb3
│ ├── dabusb
│ ├── dsp56k
│ ├── e100
│ ├── edgeport
│ ├── emi26
│ ├── emi62
│ ├── ess
│ ├── kaweth
│ ├── keyspan
│ ├── keyspan_pda
│ ├── korg
│ ├── matrox
│ ├── myricom
│ ├── ositech
│ ├── qlogic
│ ├── r128
│ ├── radeon
│ ├── sb16
│ ├── sun
│ ├── tehuti
│ ├── tigon
│ ├── ttusb-budget
│ ├── vicam
│ ├── yam
│ └── yamaha
├── fs
│ ├── 9p
│ ├── adfs
│ ├── affs
│ ├── afs
│ ├── autofs4
│ ├── befs
│ ├── bfs
│ ├── btrfs
│ ├── cachefiles
│ ├── ceph
│ ├── cifs
│ ├── coda
│ ├── configfs
│ ├── cramfs
│ ├── debugfs
│ ├── devpts
│ ├── dlm
│ ├── ecryptfs
│ ├── efs
│ ├── exofs
│ ├── exportfs
│ ├── ext2
│ ├── ext3
│ ├── ext4
│ ├── fat
│ ├── freevxfs
│ ├── fscache
│ ├── fuse
│ ├── gfs2
│ ├── hfs
│ ├── hfsplus
│ ├── hostfs
│ ├── hpfs
│ ├── hppfs
│ ├── hugetlbfs
│ ├── isofs
│ ├── jbd
│ ├── jbd2
│ ├── jffs2
│ ├── jfs
│ ├── lockd
│ ├── logfs
│ ├── minix
│ ├── ncpfs
│ ├── nfs
│ ├── nfs_common
│ ├── nfsd
│ ├── nilfs2
│ ├── nls
│ ├── notify
│ ├── ntfs
│ ├── ocfs2
│ ├── omfs
│ ├── openpromfs
│ ├── partitions
│ ├── proc
│ ├── qnx4
│ ├── quota
│ ├── ramfs
│ ├── reiserfs
│ ├── romfs
│ ├── squashfs
│ ├── sysfs
│ ├── sysv
│ ├── ubifs
│ ├── udf
│ ├── ufs
│ └── xfs
├── include
│ ├── acpi
│ ├── asm-generic
│ ├── crypto
│ ├── drm
│ ├── keys
│ ├── linux
│ ├── math-emu
│ ├── media
│ ├── mtd
│ ├── net
│ ├── pcmcia
│ ├── rdma
│ ├── rxrpc
│ ├── scsi
│ ├── sound
│ ├── trace
│ ├── video
│ └── xen
├── init
├── ipc
├── kernel
│ ├── debug
│ ├── gcov
│ ├── irq
│ ├── power
│ ├── time
│ └── trace
├── lib
│ ├── lzo
│ ├── raid6
│ ├── reed_solomon
│ ├── zlib_deflate
│ └── zlib_inflate
├── meta
│ ├── conf
│ ├── lib
│ ├── recipes-core
│ ├── recipes-gnome
│ ├── recipes-graphics
│ └── recipes-kernel
├── mm
├── net
│ ├── 802
│ ├── 8021q
│ ├── 9p
│ ├── appletalk
│ ├── atm
│ ├── ax25
│ ├── bluetooth
│ ├── bridge
│ ├── caif
│ ├── can
│ ├── ceph
│ ├── core
│ ├── dcb
│ ├── dccp
│ ├── decnet
│ ├── dns_resolver
│ ├── dsa
│ ├── econet
│ ├── ethernet
│ ├── ieee802154
│ ├── ipv4
│ ├── ipv6
│ ├── ipx
│ ├── irda
│ ├── iucv
│ ├── key
│ ├── l2tp
│ ├── lapb
│ ├── llc
│ ├── mac80211
│ ├── netfilter
│ ├── netlabel
│ ├── netlink
│ ├── netrom
│ ├── packet
│ ├── phonet
│ ├── rds
│ ├── rfkill
│ ├── rose
│ ├── rxrpc
│ ├── sched
│ ├── sctp
│ ├── sunrpc
│ ├── tipc
│ ├── unix
│ ├── wanrouter
│ ├── wimax
│ ├── wireless
│ ├── x25
│ └── xfrm
├── samples
│ ├── hw_breakpoint
│ ├── kdb
│ ├── kfifo
│ ├── kobject
│ ├── kprobes
│ ├── markers
│ ├── trace_events
│ └── tracepoints
├── scripts
│ ├── basic
│ ├── coccinelle
│ ├── dtc
│ ├── genksyms
│ ├── kconfig
│ ├── ksymoops
│ ├── mod
│ ├── package
│ ├── rt-tester
│ ├── selinux
│ └── tracing
├── security
│ ├── apparmor
│ ├── integrity
│ ├── keys
│ ├── selinux
│ ├── smack
│ └── tomoyo
├── sound
│ ├── aoa
│ ├── arm
│ ├── atmel
│ ├── core
│ ├── drivers
│ ├── i2c
│ ├── isa
│ ├── mips
│ ├── oss
│ ├── parisc
│ ├── pci
│ ├── pcmcia
│ ├── ppc
│ ├── sh
│ ├── soc
│ ├── sparc
│ ├── spi
│ ├── synth
│ └── usb
├── tools
│ ├── firewire
│ ├── perf
│ └── usb
├── usr
└── virt
└── kvm
463 directories
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-21 14:03 ` chinmaya hoshing
@ 2011-09-21 16:10 ` Bruce Ashfield
2011-09-22 8:39 ` chinmaya hoshing
0 siblings, 1 reply; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-21 16:10 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On 11-09-21 10:03 AM, chinmaya hoshing wrote:
>
> Hi ,
>
> I am not doing any changes to kernel, following are the thing what I did :-
>
> 1. I cloned poky from ( git://git.yoctoproject.org/poky ) and using
> bernard <http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=bernard>
> branch.
> 2. I pull some packages from openembeded and also create my own.
> 3. I maintained git repository for my poky source and did git commit for
> all for my changes.
Are you talking about committing kernel changes here ? Or changes
to layers and packages ?
> 4. I created a local git and ftp repo on my local machine and modify the
> related recipes (SRC_URI ) as I don't want to waste my band width by
> downloaing packages while building again and again.
>
>
> Now I have a local the git repository for linux-yocto from
> git://git.yoctoproject.org/linux-yocto-3.0
> <git://git.yoctoproject.org/linux-yocto-3.0 >
> Now I modify the linux-yocto_git.bb <http://linux-yocto_git.bb> as
> follows :-
> -
> git://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
> <http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
> +
> git://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
> <http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>
> Every package is building fine even u-boot but, while building
> linux-yocto I got error as "No such file or directory update-modules,
> scripts/bitbake " ( some more dirs ).
>
> When I examine the source tree for poky I found out that linux-yocto
> source is fetched in side the poky source and modifying the poky source
> tree.
I'm not following what you are describing here. Linux-yocto works largely
like any other git based recipe. It works from the copy of the repo
that is created in downloads/git2 and does a slightly different
instantiation into ${B} to ensure that all branches are local. If
you don't have the right code in in the downloaded git repo, or a
tarball created from it, you won't see it in your build.
>
> The modification also removing the poky recipes directories like
> recipes-multimedia recipes-sato and so on .
>
> I am also attaching the tree for both i.e original poky tree and after
> pulling linux-yocto poky tree
Can you clarify what this is showing ? missing changes you
made to the kernel ? Perhaps a diff would illustrate it better.
Bruce
>
>
> Regards
> Chinmaya
>
> On Wed, Sep 21, 2011 at 6:00 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>> wrote:
>
> On Wed, Sep 21, 2011 at 12:49 AM, chinmaya hoshing
> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>> wrote:
> > Hi ,
> > I have setup a git server that is clone of linux-yocto-3.0 from
> > git://git.yoctoproject.org/linux-yocto-3.0
> <http://git.yoctoproject.org/linux-yocto-3.0> repository.
>
> That's good! So where are you pushing your changes ? To that repo ? Are
> you updating the SRCREV or using AUTOREV in your local layers ? I use
> this workflow everyday, so it does work. I just need to understand
> where you
> are putting your changes, and then we'll know why you aren't seeing them
> on subsequent builds (or we'll have more ideas about where to look).
>
> Cheers,
>
> Bruce
>
> > Regards
> > C Hoshing
> >
> > On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>>
> > wrote:
> >>
> >> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing
> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>>
> >> wrote:
> >> > Hi ,
> >> > I have set up a git server for linux-yocto.
> >> > Following is my recipe :
> >> > require linux-yocto.inc
> >> > KMACHINE = "yocto/standard/base"
> >> > KMACHINE_qemux86 = "yocto/standard/common-pc/base"
> >> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
> >> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> >> > KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
> >> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> >> > KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
> >> > KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
> >> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
> >> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
> >> > KMACHINE_fishriver = "yocto/standard/fishriver"
> >> > KBRANCH = ${KMACHINE}
> >> > KMETA = meta
> >> > LINUX_VERSION ?= "3.0"
> >> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> >> > PR = "r0"
> >> > #PV = "${LINUX_VERSION}+git${SRCPV}"
> >> > #SRCREV_FORMAT = "meta_machine"
> >> > SRC_URI =
> >> >
> >> >
> "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
> >> >
> >> > COMPATIBLE_MACHINE =
> >> >
> >> >
> "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
> >> > # Functionality flags
> >> > KERNEL_REVISION_CHECKING ?= "t"
> >> > KERNEL_FEATURES="features/netfilter"
> >> > KERNEL_FEATURES_append_qemux86=" cfg/sound"
> >> > KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> >> > YOCTO_KERNEL_META_DATA=t
> >> > # Temporary fix for oprofile and latencytop on qemux86-64
> >> > KERNEL_FEATURES_append_qemux86-64=" features/profiling"
> >> > KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
> >> > # extra tasks
> >> > addtask kernel_link_vmlinux after do_compile before do_install
> >> > addtask validate_branches before do_patch after do_kernel_checkout
> >> > addtask kernel_configcheck after do_configure before do_compile
> >> > require linux-tools.inc
> >> >
> >> >
> >> > But still I am getting the same result as before . My previous git
> >> > commits
> >> > in poky source are flashed out , also the only recipe remains in
> >> > meta/recipe-kernel/ is linux .
> >>
> >> Just so I'm clear here. Are you still working with tarballs of the
> >> source, or have
> >> you setup a git server that is a clone of the linux-yocto-3.0 (as an
> >> example) tree ?
> >>
> >> Where are you putting your changes in this scenario ?
> >>
> >> Bruce
> >>
> >> >
> >> > Regards
> >> > C Hoshing
> >> >
> >> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas
> <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
> >> >>
> >> >> On 2011-09-16 09:06, Richard Purdie wrote:
> >> >>>
> >> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
> >> >>>>
> >> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
> >> >>>> <bruce.ashfield@gmail.com
> <mailto:bruce.ashfield@gmail.com>> wrote:
> >> >>>>>
> >> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya
> >> >>>>> hoshing<cahoshing@gmail.com <mailto:cahoshing@gmail.com>>
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> Hi ,
> >> >>>>>> I am building poky-build minimal live image for fishriver
> machine
> >> >>>>>> on
> >> >>>>>> 64 bit
> >> >>>>>> host machine.
> >> >>>>>> As I am having limited internet band-width, so I have
> identified
> >> >>>>>> all
> >> >>>>>> the
> >> >>>>>> dependent packages and setup a Apache server on my local
> system so
> >> >>>>>> that I
> >> >>>>>> can redirect the SRC_URI of all the packages to my local
> server.
> >> >>>>>> I have changed the related recipes to build minimal live
> image,
> >> >>>>>> and
> >> >>>>>> modify
> >> >>>>>> bitbake.conf to add
> LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
> >> >>>>>> side
> >> >>>>>> packages I have tars which was present "build/download"
> folder.
> >> >>>>>> While building linux-yocto, fetch and unpack was done but
> during
> >> >>>>>> kernel
> >> >>>>>> checkout whatever git commits I have done previously in
> poky source
> >> >>>>>> were
> >> >>>>>> flashed out (lost), also the only recipe remains in
> >> >>>>>> meta/recipe-kernel/ is
> >> >>>>>> linux .
> >> >>>>>>
> >> >>>>>> Following are the changes made in
> >> >>>>>> meta/recipes-kernel/linux/linux-yocto_git.bb
> <http://linux-yocto_git.bb>
> >> >>>>>> #SRCREV_FORMAT = "meta_machine"
> >> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> >> >>>>>> // This tar file I took from
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> >> >>>>>> PV = "${LINUX_VERSION}"
> >> >>>>>> In file
> meta-intel/meta-fishriver/conf/machine/fishriver.conf I
> >> >>>>>> modified
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >> >>>>>>
> >> >>>>>> Can any one help me to find the solution that if I had to
> pull
> >> >>>>>> linux
> >> >>>>>> kernel
> >> >>>>>> source from tar file or such and not from git repository.
> What
> >> >>>>>> things
> >> >>>>>> I have
> >> >>>>>> to do.
> >> >>>>>
> >> >>>>> The linux-yocto recipes are designed from the ground up to
> work on a
> >> >>>>> git
> >> >>>>> based repository, and there's really no way to get around
> that fact
> >> >>>>> (and no
> >> >>>>> plans to make any changes in this area).
> >> >>>>
> >> >>>> Thinking further about this, if the tgz actually was just a
> tarball
> >> >>>> of
> >> >>>> the git
> >> >>>> repositories (including the git blobs), it could work.
> >> >>>
> >> >>> This is exactly what we use behind the scenes for mirroring
> the git
> >> >>> repositories so this should work. It should be possible to
> use our
> >> >>> existing PREMIRROR code to avoid having to rewrite
> individual recipes
> >> >>> though.
> >> >>>
> >> >>> It will firstly unpack the tarball, then access whether the
> revisions
> >> >>> it
> >> >>> needs are present. If they're not, it will then (and only
> then) try
> >> >>> and
> >> >>> fetch them over the network. If the tarball is complete it will
> >> >>> therefore not touch the network. If its incomplete it will
> only fetch
> >> >>> the different (delta).
> >> >>
> >> >> This does work as advertised - I use it exclusively. I have a
> local
> >> >> package cache which I use with PREMIRROR and I set
> BB_NO_NETWORK to
> >> >> prove/protect that no network access is required.
> >> >>
> >> >> --
> >> >> ------------------------------------------------------------
> >> >> Gary Thomas | Consulting for the
> >> >> MLB Associates | Embedded world
> >> >> ------------------------------------------------------------
> >> >> _______________________________________________
> >> >> poky mailing list
> >> >> poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> >> >> https://lists.yoctoproject.org/listinfo/poky
> >> >
> >> >
> >> > _______________________________________________
> >> > poky mailing list
> >> > poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> >> > https://lists.yoctoproject.org/listinfo/poky
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> "Thou shalt not follow the NULL pointer, for chaos and madness await
> >> thee at its end"
> >
> >
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-21 16:10 ` Bruce Ashfield
@ 2011-09-22 8:39 ` chinmaya hoshing
2011-09-22 14:50 ` Bruce Ashfield
0 siblings, 1 reply; 18+ messages in thread
From: chinmaya hoshing @ 2011-09-22 8:39 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: poky
[-- Attachment #1: Type: text/plain, Size: 15980 bytes --]
On Wed, Sep 21, 2011 at 9:40 PM, Bruce Ashfield <
bruce.ashfield@windriver.com> wrote:
> On 11-09-21 10:03 AM, chinmaya hoshing wrote:
>
>>
>> Hi ,
>>
>> I am not doing any changes to kernel, following are the thing what I did
>> :-
>>
>> 1. I cloned poky from ( git://git.yoctoproject.org/**poky<http://git.yoctoproject.org/poky>) and using
>> bernard <http://git.yoctoproject.org/**cgit/cgit.cgi/poky/log/?h=**
>> bernard <http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=bernard>>
>>
>> branch.
>> 2. I pull some packages from openembeded and also create my own.
>> 3. I maintained git repository for my poky source and did git commit for
>> all for my changes.
>>
>
> >>>Are you talking about committing kernel changes here ? Or changes
> >>>to layers and packages ?
>
No I am not Commiting kernel changes here ,I am commiting packages
which are pulled in poky source
eg-
${POKY_SOURCE}/
(it contains) bitbake LICENSE meta-intel README build meta
meta-rt README.hardware documentation meta-demoapps poky-init-build-env
scripts
Before modifying the linux-yocto recipe the source extracted in
${POKY_SOURCE}/build/tmp/work/fishriver-poky-linux/linux-yocto-3.0+git1+7782fc673afd6a1c742409896ae787560d96fce8_1+c111526f70815ceff495bab07df64c0cee494d8a-r0/
linux-fishriver-standard-build
(it contains) : arch block crypto drivers firmware fs include
init ipc kernel lib Makefile mm modules.builtin modules.order
Module.symvers net scripts
security sound source System.map usr vmlinux
vmlinux.o
After modifying the linux-yocto recipe (for local server) , I
observer that the source instead of being extracted to the above mentioned
path in WORKDIR is being extracted in ${POKY_SOURCE} itself
${POKY_SOURCE}/
(it contains): arch Documentation Kbuild scripts bitbake drivers
Kconfig security block firmware kernel sound build fs lib net
tools COPYING include
MAINTAINERS README usr CREDITS init Makefile
REPORTING-BUGS
virt crypto ipc meta samples
This causes the .git folder present in kernel source to overwrite my
.git directory present in ${POKY_SOURCE} resulting in loss of my git commits
I made following changes to linux-yocto_git.bb as follows :-
- git://
git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
+ git://
192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
> 4. I created a local git and ftp repo on my local machine and modify the
>> related recipes (SRC_URI ) as I don't want to waste my band width by
>> downloaing packages while building again and again.
>>
>>
>> Now I have a local the git repository for linux-yocto from
>> git://git.yoctoproject.org/**linux-yocto-3.0<http://git.yoctoproject.org/linux-yocto-3.0>
>> <git://git.yoctoproject.org/**linux-yocto-3.0<http://git.yoctoproject.org/linux-yocto-3.0>>
>> Now I modify the linux-yocto_git.bb <http://linux-yocto_git.bb> as
>>
>> follows :-
>> -
>> git://git.pokylinux.org/linux-**yocto-3.0;protocol=git;**
>> nocheckout=1;branch=$%**7BKBRANCH%7D,meta;name=**machine,meta<http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>> <http://git.pokylinux.org/**linux-yocto-3.0;protocol=git;**
>> nocheckout=1;branch=$%**7BKBRANCH%7D,meta;name=**machine,meta<http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>> >
>>
>> +
>> git://192.168.128.11/linux-**yocto-3.0.git;protocol=git;**
>> nocheckout=1;branch=$%**7BKBRANCH%7D,meta;name=**machine,meta<http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>> <http://192.168.128.11/linux-**yocto-3.0.git;protocol=git;**
>> nocheckout=1;branch=$%**7BKBRANCH%7D,meta;name=**machine,meta<http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>> >
>>
>>
>> Every package is building fine even u-boot but, while building
>> linux-yocto I got error as "No such file or directory update-modules,
>> scripts/bitbake " ( some more dirs ).
>>
>> When I examine the source tree for poky I found out that linux-yocto
>> source is fetched in side the poky source and modifying the poky source
>> tree.
>>
>
> >>>I'm not following what you are describing here. Linux-yocto works
> largely
> >>>like any other git based recipe. It works from the copy of the repo
> >>>that is created in downloads/git2 and does a slightly different
> >>>instantiation into ${B} to ensure that all branches are local. If
> >>>you don't have the right code in in the downloaded git repo, or a
> >>>tarball created from it, you won't see it in your build.
>
>
>
>> The modification also removing the poky recipes directories like
>> recipes-multimedia recipes-sato and so on .
>>
>> I am also attaching the tree for both i.e original poky tree and after
>> pulling linux-yocto poky tree
>>
>
> >>>Can you clarify what this is showing ? missing changes you
> >>>made to the kernel ? Perhaps a diff would illustrate it better.
>
> Bruce
>
>
>>
>> Regards
>> Chinmaya
>>
>> On Wed, Sep 21, 2011 at 6:00 PM, Bruce Ashfield
>> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.**com<bruce.ashfield@gmail.com>>>
>> wrote:
>>
>> On Wed, Sep 21, 2011 at 12:49 AM, chinmaya hoshing
>> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>> wrote:
>> > Hi ,
>> > I have setup a git server that is clone of linux-yocto-3.0 from
>> > git://git.yoctoproject.org/**linux-yocto-3.0<http://git.yoctoproject.org/linux-yocto-3.0>
>> <http://git.yoctoproject.org/**linux-yocto-3.0<http://git.yoctoproject.org/linux-yocto-3.0>>
>> repository.
>>
>>
>> That's good! So where are you pushing your changes ? To that repo ? Are
>> you updating the SRCREV or using AUTOREV in your local layers ? I use
>> this workflow everyday, so it does work. I just need to understand
>> where you
>> are putting your changes, and then we'll know why you aren't seeing
>> them
>> on subsequent builds (or we'll have more ideas about where to look).
>>
>> Cheers,
>>
>> Bruce
>>
>> > Regards
>> > C Hoshing
>> >
>> > On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield
>> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.**com<bruce.ashfield@gmail.com>
>> >>
>>
>> > wrote:
>> >>
>> >> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing
>> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>>
>>
>> >> wrote:
>> >> > Hi ,
>> >> > I have set up a git server for linux-yocto.
>> >> > Following is my recipe :
>> >> > require linux-yocto.inc
>> >> > KMACHINE = "yocto/standard/base"
>> >> > KMACHINE_qemux86 = "yocto/standard/common-pc/**base"
>> >> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/**base"
>> >> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
>> >> > KMACHINE_qemumips = "yocto/standard/mti-malta32-**be"
>> >> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-**926ejs"
>> >> > KMACHINE_atom-pc = "yocto/standard/common-pc/**atom-pc"
>> >> > KMACHINE_routerstationpro = "yocto/standard/**routerstationpro"
>> >> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-**rdb"
>> >> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
>> >> > KMACHINE_fishriver = "yocto/standard/fishriver"
>> >> > KBRANCH = ${KMACHINE}
>> >> > KMETA = meta
>> >> > LINUX_VERSION ?= "3.0"
>> >> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
>> >> > PR = "r0"
>> >> > #PV = "${LINUX_VERSION}+git${SRCPV}"
>> >> > #SRCREV_FORMAT = "meta_machine"
>> >> > SRC_URI =
>> >> >
>> >> >
>> "git://xxx.xxx.xxx.xx/linux-**yocto-3.0.git;protocol=git;**
>> nocheckout=1;branch=$%**7BKBRANCH%7D,meta;name=**machine,meta"
>> >> >
>> >> > COMPATIBLE_MACHINE =
>> >> >
>> >> >
>> "(qemuarm|qemux86|qemuppc|**qemumips|qemux86-64|mpc8315e-**
>> rdb|routerstationpro|**beagleboard)"
>> >> > # Functionality flags
>> >> > KERNEL_REVISION_CHECKING ?= "t"
>> >> > KERNEL_FEATURES="features/**netfilter"
>> >> > KERNEL_FEATURES_append_**qemux86=" cfg/sound"
>> >> > KERNEL_FEATURES_append_**qemux86-64=" cfg/sound"
>> >> > YOCTO_KERNEL_META_DATA=t
>> >> > # Temporary fix for oprofile and latencytop on qemux86-64
>> >> > KERNEL_FEATURES_append_**qemux86-64=" features/profiling"
>> >> > KERNEL_FEATURES_append_**qemux86-64=" features/latencytop"
>> >> > # extra tasks
>> >> > addtask kernel_link_vmlinux after do_compile before do_install
>> >> > addtask validate_branches before do_patch after
>> do_kernel_checkout
>> >> > addtask kernel_configcheck after do_configure before do_compile
>> >> > require linux-tools.inc
>> >> >
>> >> >
>> >> > But still I am getting the same result as before . My previous
>> git
>> >> > commits
>> >> > in poky source are flashed out , also the only recipe remains in
>> >> > meta/recipe-kernel/ is linux .
>> >>
>> >> Just so I'm clear here. Are you still working with tarballs of the
>> >> source, or have
>> >> you setup a git server that is a clone of the linux-yocto-3.0 (as
>> an
>> >> example) tree ?
>> >>
>> >> Where are you putting your changes in this scenario ?
>> >>
>> >> Bruce
>> >>
>> >> >
>> >> > Regards
>> >> > C Hoshing
>> >> >
>> >> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas
>> <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>> >> >>
>> >> >> On 2011-09-16 09:06, Richard Purdie wrote:
>> >> >>>
>> >> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
>> >> >>>>
>> >> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
>> >> >>>> <bruce.ashfield@gmail.com
>> <mailto:bruce.ashfield@gmail.**com <bruce.ashfield@gmail.com>>> wrote:
>> >> >>>>>
>> >> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya
>> >> >>>>> hoshing<cahoshing@gmail.com <mailto:cahoshing@gmail.com>>
>>
>> >> >>>>> wrote:
>> >> >>>>>>
>> >> >>>>>> Hi ,
>> >> >>>>>> I am building poky-build minimal live image for fishriver
>> machine
>> >> >>>>>> on
>> >> >>>>>> 64 bit
>> >> >>>>>> host machine.
>> >> >>>>>> As I am having limited internet band-width, so I have
>> identified
>> >> >>>>>> all
>> >> >>>>>> the
>> >> >>>>>> dependent packages and setup a Apache server on my local
>> system so
>> >> >>>>>> that I
>> >> >>>>>> can redirect the SRC_URI of all the packages to my local
>> server.
>> >> >>>>>> I have changed the related recipes to build minimal live
>> image,
>> >> >>>>>> and
>> >> >>>>>> modify
>> >> >>>>>> bitbake.conf to add
>> LOCAL_MIRROR="xxx.xxx.xxx.xxx/**packages" , in
>> >> >>>>>> side
>> >> >>>>>> packages I have tars which was present "build/download"
>> folder.
>> >> >>>>>> While building linux-yocto, fetch and unpack was done but
>> during
>> >> >>>>>> kernel
>> >> >>>>>> checkout whatever git commits I have done previously in
>> poky source
>> >> >>>>>> were
>> >> >>>>>> flashed out (lost), also the only recipe remains in
>> >> >>>>>> meta/recipe-kernel/ is
>> >> >>>>>> linux .
>> >> >>>>>>
>> >> >>>>>> Following are the changes made in
>> >> >>>>>> meta/recipes-kernel/linux/linu**x-yocto_git.bb<http://linux-yocto_git.bb>
>> <http://linux-yocto_git.bb>
>>
>> >> >>>>>> #SRCREV_FORMAT = "meta_machine"
>> >> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-**3.0-3.0.tar.bz2"
>> >> >>>>>> // This tar file I took from
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>
>> http://git.yoctoproject.org/**cgit/cgit.cgi/linux-yocto-3.0/**
>> snapshot/linux-yocto-3.0-3.0.**tar.bz2<http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2>
>> >> >>>>>> PV = "${LINUX_VERSION}"
>> >> >>>>>> In file
>> meta-intel/meta-fishriver/**conf/machine/fishriver.conf I
>> >> >>>>>> modified
>> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
>> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>> >> >>>>>>
>> >> >>>>>> Can any one help me to find the solution that if I had to
>> pull
>> >> >>>>>> linux
>> >> >>>>>> kernel
>> >> >>>>>> source from tar file or such and not from git repository.
>> What
>> >> >>>>>> things
>> >> >>>>>> I have
>> >> >>>>>> to do.
>> >> >>>>>
>> >> >>>>> The linux-yocto recipes are designed from the ground up to
>> work on a
>> >> >>>>> git
>> >> >>>>> based repository, and there's really no way to get around
>> that fact
>> >> >>>>> (and no
>> >> >>>>> plans to make any changes in this area).
>> >> >>>>
>> >> >>>> Thinking further about this, if the tgz actually was just a
>> tarball
>> >> >>>> of
>> >> >>>> the git
>> >> >>>> repositories (including the git blobs), it could work.
>> >> >>>
>> >> >>> This is exactly what we use behind the scenes for mirroring
>> the git
>> >> >>> repositories so this should work. It should be possible to
>> use our
>> >> >>> existing PREMIRROR code to avoid having to rewrite
>> individual recipes
>> >> >>> though.
>> >> >>>
>> >> >>> It will firstly unpack the tarball, then access whether the
>> revisions
>> >> >>> it
>> >> >>> needs are present. If they're not, it will then (and only
>> then) try
>> >> >>> and
>> >> >>> fetch them over the network. If the tarball is complete it will
>> >> >>> therefore not touch the network. If its incomplete it will
>> only fetch
>> >> >>> the different (delta).
>> >> >>
>> >> >> This does work as advertised - I use it exclusively. I have a
>> local
>> >> >> package cache which I use with PREMIRROR and I set
>> BB_NO_NETWORK to
>> >> >> prove/protect that no network access is required.
>> >> >>
>> >> >> --
>> >> >> ------------------------------**------------------------------
>> >> >> Gary Thomas | Consulting for the
>> >> >> MLB Associates | Embedded world
>> >> >> ------------------------------**------------------------------
>> >> >> ______________________________**_________________
>> >> >> poky mailing list
>> >> >> poky@yoctoproject.org <mailto:poky@yoctoproject.org>
>>
>> >> >> https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>
>> >> >
>> >> >
>> >> > ______________________________**_________________
>> >> > poky mailing list
>> >> > poky@yoctoproject.org <mailto:poky@yoctoproject.org>
>>
>> >> > https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> "Thou shalt not follow the NULL pointer, for chaos and madness
>> await
>> >> thee at its end"
>> >
>> >
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>>
>>
>>
>>
>> ______________________________**_________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>
>>
>
>
[-- Attachment #2: Type: text/html, Size: 26534 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-22 8:39 ` chinmaya hoshing
@ 2011-09-22 14:50 ` Bruce Ashfield
0 siblings, 0 replies; 18+ messages in thread
From: Bruce Ashfield @ 2011-09-22 14:50 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On 11-09-22 04:39 AM, chinmaya hoshing wrote:
>
>
> On Wed, Sep 21, 2011 at 9:40 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
> On 11-09-21 10:03 AM, chinmaya hoshing wrote:
>
>
> Hi ,
>
> I am not doing any changes to kernel, following are the thing
> what I did :-
>
> 1. I cloned poky from ( git://git.yoctoproject.org/__poky
> <http://git.yoctoproject.org/poky> ) and using
> bernard
> <http://git.yoctoproject.org/__cgit/cgit.cgi/poky/log/?h=__bernard
> <http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=bernard>>
>
> branch.
> 2. I pull some packages from openembeded and also create my own.
> 3. I maintained git repository for my poky source and did git
> commit for
> all for my changes.
>
>
> > >>Are you talking about committing kernel changes here ? Or changes
> > >>to layers and packages ?
>
> No I am not Commiting kernel changes here ,I am commiting packages which
> are pulled in poky source
>
> eg-
> ${POKY_SOURCE}/
> (it contains) bitbake LICENSE meta-intel README build meta meta-rt
> README.hardware documentation meta-demoapps poky-init-build-env scripts
> Before modifying the linux-yocto recipe the source extracted in
> ${POKY_SOURCE}/build/tmp/work/fishriver-poky-linux/linux-yocto-3.0+git1+7782fc673afd6a1c742409896ae787560d96fce8_1+c111526f70815ceff495bab07df64c0cee494d8a-r0/
>
> linux-fishriver-standard-build
> (it contains) : arch block crypto drivers firmware fs include init ipc
> kernel lib Makefile mm modules.builtin modules.order Module.symvers net
> scripts
> security sound source System.map usr vmlinux vmlinux.o
>
> After modifying the linux-yocto recipe (for local server) , I observer
> that the source instead of being extracted to the above mentioned path
> in WORKDIR is being extracted in ${POKY_SOURCE} itself
> ${POKY_SOURCE}/
> (it contains): arch Documentation Kbuild scripts bitbake drivers Kconfig
> security block firmware kernel sound build fs lib net tools COPYING include
> MAINTAINERS README usr CREDITS init Makefile REPORTING-BUGS virt crypto
> ipc meta samples
> This causes the .git folder present in kernel source to overwrite my
> .git directory present in ${POKY_SOURCE} resulting in loss of my git commits
Aha. It is now clear to me. This is completely different than
what I was thinking.
This (to me) looks to be in the middle of the fetcher code, so we
need someone with more knowledge in this area to comment. But the
only way I can see that happening is is ${B} ends up pointing
to the wrong location.
Bruce
> I made following changes to linux-yocto_git.bb
> <http://linux-yocto_git.bb> as follows :-
> -git://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
> <http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
> +
> git://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta
> <http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
>
> 4. I created a local git and ftp repo on my local machine and
> modify the
> related recipes (SRC_URI ) as I don't want to waste my band width by
> downloaing packages while building again and again.
>
>
> Now I have a local the git repository for linux-yocto from
> git://git.yoctoproject.org/__linux-yocto-3.0
> <http://git.yoctoproject.org/linux-yocto-3.0>
> <git://git.yoctoproject.org/__linux-yocto-3.0
> <http://git.yoctoproject.org/linux-yocto-3.0> >
> Now I modify the linux-yocto_git.bb <http://linux-yocto_git.bb>
> <http://linux-yocto_git.bb> as
>
> follows :-
> -
> git://git.pokylinux.org/linux-__yocto-3.0;protocol=git;__nocheckout=1;branch=$%__7BKBRANCH%7D,meta;name=__machine,meta
> <http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
> <http://git.pokylinux.org/__linux-yocto-3.0;protocol=git;__nocheckout=1;branch=$%__7BKBRANCH%7D,meta;name=__machine,meta
> <http://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>>
>
> +
> git://192.168.128.11/linux-__yocto-3.0.git;protocol=git;__nocheckout=1;branch=$%__7BKBRANCH%7D,meta;name=__machine,meta
> <http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>
> <http://192.168.128.11/linux-__yocto-3.0.git;protocol=git;__nocheckout=1;branch=$%__7BKBRANCH%7D,meta;name=__machine,meta
> <http://192.168.128.11/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta>>
>
>
> Every package is building fine even u-boot but, while building
> linux-yocto I got error as "No such file or directory
> update-modules,
> scripts/bitbake " ( some more dirs ).
>
> When I examine the source tree for poky I found out that linux-yocto
> source is fetched in side the poky source and modifying the poky
> source
> tree.
>
>
> > >>I'm not following what you are describing here. Linux-yocto works
> largely
> > >>like any other git based recipe. It works from the copy of the repo
> > >>that is created in downloads/git2 and does a slightly different
> > >>instantiation into ${B} to ensure that all branches are local. If
> > >>you don't have the right code in in the downloaded git repo, or a
> > >>tarball created from it, you won't see it in your build.
>
>
>
> The modification also removing the poky recipes directories like
> recipes-multimedia recipes-sato and so on .
>
> I am also attaching the tree for both i.e original poky tree and
> after
> pulling linux-yocto poky tree
>
>
> > >>Can you clarify what this is showing ? missing changes you
> > >>made to the kernel ? Perhaps a diff would illustrate it better.
>
> Bruce
>
>
>
> Regards
> Chinmaya
>
> On Wed, Sep 21, 2011 at 6:00 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>
> <mailto:bruce.ashfield@gmail.__com
> <mailto:bruce.ashfield@gmail.com>>> wrote:
>
> On Wed, Sep 21, 2011 at 12:49 AM, chinmaya hoshing
> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>
> <mailto:cahoshing@gmail.com <mailto:cahoshing@gmail.com>>> wrote:
> > Hi ,
> > I have setup a git server that is clone of linux-yocto-3.0 from
> > git://git.yoctoproject.org/__linux-yocto-3.0
> <http://git.yoctoproject.org/linux-yocto-3.0>
> <http://git.yoctoproject.org/__linux-yocto-3.0
> <http://git.yoctoproject.org/linux-yocto-3.0>> repository.
>
>
> That's good! So where are you pushing your changes ? To that
> repo ? Are
> you updating the SRCREV or using AUTOREV in your local layers ?
> I use
> this workflow everyday, so it does work. I just need to understand
> where you
> are putting your changes, and then we'll know why you aren't
> seeing them
> on subsequent builds (or we'll have more ideas about where to look).
>
> Cheers,
>
> Bruce
>
> > Regards
> > C Hoshing
> >
> > On Tue, Sep 20, 2011 at 7:24 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>
> <mailto:bruce.ashfield@gmail.__com
> <mailto:bruce.ashfield@gmail.com>>>
>
> > wrote:
> >>
> >> On Tue, Sep 20, 2011 at 5:51 AM, chinmaya hoshing
> <cahoshing@gmail.com <mailto:cahoshing@gmail.com>
> <mailto:cahoshing@gmail.com <mailto:cahoshing@gmail.com>>>
>
> >> wrote:
> >> > Hi ,
> >> > I have set up a git server for linux-yocto.
> >> > Following is my recipe :
> >> > require linux-yocto.inc
> >> > KMACHINE = "yocto/standard/base"
> >> > KMACHINE_qemux86 = "yocto/standard/common-pc/__base"
> >> > KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/__base"
> >> > KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> >> > KMACHINE_qemumips = "yocto/standard/mti-malta32-__be"
> >> > KMACHINE_qemuarm = "yocto/standard/arm-versatile-__926ejs"
> >> > KMACHINE_atom-pc = "yocto/standard/common-pc/__atom-pc"
> >> > KMACHINE_routerstationpro =
> "yocto/standard/__routerstationpro"
> >> > KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-__rdb"
> >> > KMACHINE_beagleboard = "yocto/standard/beagleboard"
> >> > KMACHINE_fishriver = "yocto/standard/fishriver"
> >> > KBRANCH = ${KMACHINE}
> >> > KMETA = meta
> >> > LINUX_VERSION ?= "3.0"
> >> > LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> >> > PR = "r0"
> >> > #PV = "${LINUX_VERSION}+git${SRCPV}"
> >> > #SRCREV_FORMAT = "meta_machine"
> >> > SRC_URI =
> >> >
> >> >
> "git://xxx.xxx.xxx.xx/linux-__yocto-3.0.git;protocol=git;__nocheckout=1;branch=$%__7BKBRANCH%7D,meta;name=__machine,meta"
> >> >
> >> > COMPATIBLE_MACHINE =
> >> >
> >> >
> "(qemuarm|qemux86|qemuppc|__qemumips|qemux86-64|mpc8315e-__rdb|routerstationpro|__beagleboard)"
> >> > # Functionality flags
> >> > KERNEL_REVISION_CHECKING ?= "t"
> >> > KERNEL_FEATURES="features/__netfilter"
> >> > KERNEL_FEATURES_append___qemux86=" cfg/sound"
> >> > KERNEL_FEATURES_append___qemux86-64=" cfg/sound"
> >> > YOCTO_KERNEL_META_DATA=t
> >> > # Temporary fix for oprofile and latencytop on qemux86-64
> >> > KERNEL_FEATURES_append___qemux86-64=" features/profiling"
> >> > KERNEL_FEATURES_append___qemux86-64=" features/latencytop"
> >> > # extra tasks
> >> > addtask kernel_link_vmlinux after do_compile before do_install
> >> > addtask validate_branches before do_patch after
> do_kernel_checkout
> >> > addtask kernel_configcheck after do_configure before
> do_compile
> >> > require linux-tools.inc
> >> >
> >> >
> >> > But still I am getting the same result as before . My
> previous git
> >> > commits
> >> > in poky source are flashed out , also the only recipe
> remains in
> >> > meta/recipe-kernel/ is linux .
> >>
> >> Just so I'm clear here. Are you still working with tarballs
> of the
> >> source, or have
> >> you setup a git server that is a clone of the
> linux-yocto-3.0 (as an
> >> example) tree ?
> >>
> >> Where are you putting your changes in this scenario ?
> >>
> >> Bruce
> >>
> >> >
> >> > Regards
> >> > C Hoshing
> >> >
> >> > On Fri, Sep 16, 2011 at 8:52 PM, Gary Thomas
> <gary@mlbassoc.com <mailto:gary@mlbassoc.com>
> <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com>>> wrote:
> >> >>
> >> >> On 2011-09-16 09:06, Richard Purdie wrote:
> >> >>>
> >> >>> On Fri, 2011-09-16 at 10:35 -0400, Bruce Ashfield wrote:
> >> >>>>
> >> >>>> On Fri, Sep 16, 2011 at 10:24 AM, Bruce Ashfield
> >> >>>> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>
> <mailto:bruce.ashfield@gmail.__com
> <mailto:bruce.ashfield@gmail.com>>> wrote:
> >> >>>>>
> >> >>>>> On Fri, Sep 16, 2011 at 8:38 AM, chinmaya
> >> >>>>> hoshing<cahoshing@gmail.com
> <mailto:cahoshing@gmail.com> <mailto:cahoshing@gmail.com
> <mailto:cahoshing@gmail.com>>>
>
> >> >>>>> wrote:
> >> >>>>>>
> >> >>>>>> Hi ,
> >> >>>>>> I am building poky-build minimal live image for fishriver
> machine
> >> >>>>>> on
> >> >>>>>> 64 bit
> >> >>>>>> host machine.
> >> >>>>>> As I am having limited internet band-width, so I have
> identified
> >> >>>>>> all
> >> >>>>>> the
> >> >>>>>> dependent packages and setup a Apache server on my local
> system so
> >> >>>>>> that I
> >> >>>>>> can redirect the SRC_URI of all the packages to my local
> server.
> >> >>>>>> I have changed the related recipes to build minimal live
> image,
> >> >>>>>> and
> >> >>>>>> modify
> >> >>>>>> bitbake.conf to add
> LOCAL_MIRROR="xxx.xxx.xxx.xxx/__packages" , in
> >> >>>>>> side
> >> >>>>>> packages I have tars which was present "build/download"
> folder.
> >> >>>>>> While building linux-yocto, fetch and unpack was done but
> during
> >> >>>>>> kernel
> >> >>>>>> checkout whatever git commits I have done previously in
> poky source
> >> >>>>>> were
> >> >>>>>> flashed out (lost), also the only recipe remains in
> >> >>>>>> meta/recipe-kernel/ is
> >> >>>>>> linux .
> >> >>>>>>
> >> >>>>>> Following are the changes made in
> >> >>>>>> meta/recipes-kernel/linux/linu__x-yocto_git.bb
> <http://linux-yocto_git.bb>
> <http://linux-yocto_git.bb>
>
> >> >>>>>> #SRCREV_FORMAT = "meta_machine"
> >> >>>>>> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-__3.0-3.0.tar.bz2"
> >> >>>>>> // This tar file I took from
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> http://git.yoctoproject.org/__cgit/cgit.cgi/linux-yocto-3.0/__snapshot/linux-yocto-3.0-3.0.__tar.bz2
> <http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2>
> >> >>>>>> PV = "${LINUX_VERSION}"
> >> >>>>>> In file
> meta-intel/meta-fishriver/__conf/machine/fishriver.conf I
> >> >>>>>> modified
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> >> >>>>>> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >> >>>>>>
> >> >>>>>> Can any one help me to find the solution that if I had to
> pull
> >> >>>>>> linux
> >> >>>>>> kernel
> >> >>>>>> source from tar file or such and not from git repository.
> What
> >> >>>>>> things
> >> >>>>>> I have
> >> >>>>>> to do.
> >> >>>>>
> >> >>>>> The linux-yocto recipes are designed from the ground up to
> work on a
> >> >>>>> git
> >> >>>>> based repository, and there's really no way to get around
> that fact
> >> >>>>> (and no
> >> >>>>> plans to make any changes in this area).
> >> >>>>
> >> >>>> Thinking further about this, if the tgz actually was just a
> tarball
> >> >>>> of
> >> >>>> the git
> >> >>>> repositories (including the git blobs), it could work.
> >> >>>
> >> >>> This is exactly what we use behind the scenes for mirroring
> the git
> >> >>> repositories so this should work. It should be possible to
> use our
> >> >>> existing PREMIRROR code to avoid having to rewrite
> individual recipes
> >> >>> though.
> >> >>>
> >> >>> It will firstly unpack the tarball, then access whether the
> revisions
> >> >>> it
> >> >>> needs are present. If they're not, it will then (and only
> then) try
> >> >>> and
> >> >>> fetch them over the network. If the tarball is complete
> it will
> >> >>> therefore not touch the network. If its incomplete it will
> only fetch
> >> >>> the different (delta).
> >> >>
> >> >> This does work as advertised - I use it exclusively. I have a
> local
> >> >> package cache which I use with PREMIRROR and I set
> BB_NO_NETWORK to
> >> >> prove/protect that no network access is required.
> >> >>
> >> >> --
> >> >>
> ------------------------------__------------------------------
> >> >> Gary Thomas | Consulting for the
> >> >> MLB Associates | Embedded world
> >> >>
> ------------------------------__------------------------------
> >> >> _________________________________________________
> >> >> poky mailing list
> >> >> poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> <mailto:poky@yoctoproject.org <mailto:poky@yoctoproject.org>>
>
> >> >> https://lists.yoctoproject.__org/listinfo/poky
> <https://lists.yoctoproject.org/listinfo/poky>
> >> >
> >> >
> >> > _________________________________________________
> >> > poky mailing list
> >> > poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> <mailto:poky@yoctoproject.org <mailto:poky@yoctoproject.org>>
>
> >> > https://lists.yoctoproject.__org/listinfo/poky
> <https://lists.yoctoproject.org/listinfo/poky>
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> "Thou shalt not follow the NULL pointer, for chaos and
> madness await
> >> thee at its end"
> >
> >
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
>
>
>
> _________________________________________________
> poky mailing list
> poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> https://lists.yoctoproject.__org/listinfo/poky
> <https://lists.yoctoproject.org/listinfo/poky>
>
>
>
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-16 12:38 Getting error in linux-yocto kernel during build chinmaya hoshing
2011-09-16 14:24 ` Bruce Ashfield
@ 2011-09-27 4:28 ` Darren Hart
2011-10-03 4:54 ` chinmaya hoshing
1 sibling, 1 reply; 18+ messages in thread
From: Darren Hart @ 2011-09-27 4:28 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On 09/16/2011 05:38 AM, chinmaya hoshing wrote:
> Hi ,
>
> I am building poky-build minimal live image for fishriver machine on 64
> bit host machine.
> As I am having limited internet band-width, so I have identified all the
> dependent packages and setup a Apache server on my local system so that
> I can redirect the SRC_URI of all the packages to my local server.
> I have changed the related recipes to build minimal live image, and
> modify bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
> side packages I have tars which was present "build/download" folder.
OK... why not just use a common download directory? From what you've
described your just trying to speed up the build on a single build system.
--
Darren
>
> While building linux-yocto, fetch and unpack was done but during kernel
> checkout whatever git commits I have done previously in poky source were
> flashed out (lost), also the only recipe remains in
> meta/recipe-kernel/ is linux .
>
>
> Following are the changes made in
> meta/recipes-kernel/linux/linux-yocto_git.bb <http://linux-yocto_git.bb>
> #SRCREV_FORMAT = "meta_machine"
> SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> // This tar file I took from
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> PV = "${LINUX_VERSION}"
>
> In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
> PREFERRED_VERSION_linux-yocto = "3.0" (which was
> PREFERRED_VERSION_linux-yocto = "3.0+git%" )
>
>
> Can any one help me to find the solution that if I had to pull linux
> kernel source from tar file or such and not from git repository. What
> things I have to do.
>
> Regards
> C Hoshing
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-20 9:51 ` chinmaya hoshing
2011-09-20 13:54 ` Bruce Ashfield
@ 2011-09-27 4:40 ` Darren Hart
1 sibling, 0 replies; 18+ messages in thread
From: Darren Hart @ 2011-09-27 4:40 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On 09/20/2011 02:51 AM, chinmaya hoshing wrote:
> Hi ,
>
> I have set up a git server for linux-yocto.
Did you do a --bare clone?
>
> Following is my recipe :
Is there a reason you are recreating the entire recipe instead of just
adding a layer which only makes the necessary changes in a bbappend file?
> require linux-yocto.inc
>
> KMACHINE = "yocto/standard/base"
> KMACHINE_qemux86 = "yocto/standard/common-pc/base"
> KMACHINE_qemux86-64 = "yocto/standard/common-pc-64/base"
> KMACHINE_qemuppc = "yocto/standard/qemu-ppc32"
> KMACHINE_qemumips = "yocto/standard/mti-malta32-be"
> KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> KMACHINE_atom-pc = "yocto/standard/common-pc/atom-pc"
> KMACHINE_routerstationpro = "yocto/standard/routerstationpro"
> KMACHINE_mpc8315e-rdb = "yocto/standard/fsl-mpc8315e-rdb"
> KMACHINE_beagleboard = "yocto/standard/beagleboard"
> KMACHINE_fishriver = "yocto/standard/fishriver"
>
> KBRANCH = ${KMACHINE}
> KMETA = meta
>
> LINUX_VERSION ?= "3.0"
> LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> PR = "r0"
> #PV = "${LINUX_VERSION}+git${SRCPV}"
> #SRCREV_FORMAT = "meta_machine"
>
> SRC_URI =
> "git://xxx.xxx.xxx.xx/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=$%7BKBRANCH%7D,meta;name=machine,meta"
>
> COMPATIBLE_MACHINE =
> "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|mpc8315e-rdb|routerstationpro|beagleboard)"
>
> # Functionality flags
> KERNEL_REVISION_CHECKING ?= "t"
> KERNEL_FEATURES="features/netfilter"
> KERNEL_FEATURES_append_qemux86=" cfg/sound"
> KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
>
> YOCTO_KERNEL_META_DATA=t
>
> # Temporary fix for oprofile and latencytop on qemux86-64
> KERNEL_FEATURES_append_qemux86-64=" features/profiling"
> KERNEL_FEATURES_append_qemux86-64=" features/latencytop"
>
> # extra tasks
> addtask kernel_link_vmlinux after do_compile before do_install
> addtask validate_branches before do_patch after do_kernel_checkout
> addtask kernel_configcheck after do_configure before do_compile
>
> require linux-tools.inc
>
>
>
> But still I am getting the same result as before . My previous git
> commits in poky source are flashed out , also the only recipe remains in
> meta/recipe-kernel/ is linux .
>
>
> Regards
> C Hoshing
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-09-27 4:28 ` Darren Hart
@ 2011-10-03 4:54 ` chinmaya hoshing
2011-10-03 15:39 ` Darren Hart
0 siblings, 1 reply; 18+ messages in thread
From: chinmaya hoshing @ 2011-10-03 4:54 UTC (permalink / raw)
To: Darren Hart; +Cc: poky
[-- Attachment #1: Type: text/plain, Size: 2584 bytes --]
Hi,
In Downloads directory whatever were the entries for linux kernel
I have kept them in downloads folder while building.
After this I disconnected the network and started the build ,But it throws
error for Unable to fetch source for linux-libc-headers, whereas building my
kernel i.e linux-yocto_git.bb with this downloads does not create any
problem.
On Tue, Sep 27, 2011 at 9:58 AM, Darren Hart <dvhart@linux.intel.com> wrote:
>
>
> On 09/16/2011 05:38 AM, chinmaya hoshing wrote:
> > Hi ,
> >
> > I am building poky-build minimal live image for fishriver machine on 64
> > bit host machine.
> > As I am having limited internet band-width, so I have identified all the
> > dependent packages and setup a Apache server on my local system so that
> > I can redirect the SRC_URI of all the packages to my local server.
> > I have changed the related recipes to build minimal live image, and
> > modify bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages" , in
> > side packages I have tars which was present "build/download" folder.
>
> OK... why not just use a common download directory? From what you've
> described your just trying to speed up the build on a single build system.
>
> --
> Darren
>
> >
> > While building linux-yocto, fetch and unpack was done but during kernel
> > checkout whatever git commits I have done previously in poky source were
> > flashed out (lost), also the only recipe remains in
> > meta/recipe-kernel/ is linux .
> >
> >
> > Following are the changes made in
> > meta/recipes-kernel/linux/linux-yocto_git.bb <http://linux-yocto_git.bb>
> > #SRCREV_FORMAT = "meta_machine"
> > SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> > // This tar file I took from
> >
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> > PV = "${LINUX_VERSION}"
> >
> > In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I modified
> > PREFERRED_VERSION_linux-yocto = "3.0" (which was
> > PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >
> >
> > Can any one help me to find the solution that if I had to pull linux
> > kernel source from tar file or such and not from git repository. What
> > things I have to do.
> >
> > Regards
> > C Hoshing
> >
> >
> >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/poky
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
>
[-- Attachment #2: Type: text/html, Size: 3770 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: Getting error in linux-yocto kernel during build.
2011-10-03 4:54 ` chinmaya hoshing
@ 2011-10-03 15:39 ` Darren Hart
0 siblings, 0 replies; 18+ messages in thread
From: Darren Hart @ 2011-10-03 15:39 UTC (permalink / raw)
To: chinmaya hoshing; +Cc: poky
On 10/02/2011 09:54 PM, chinmaya hoshing wrote:
> Hi,
>
> In Downloads directory whatever were the entries for linux kernel
> I have kept them in downloads folder while building.
> After this I disconnected the network and started the build ,But it
> throws error for Unable to fetch source for linux-libc-headers, whereas
> building my kernel i.e linux-yocto_git.bb <http://linux-yocto_git.bb>
> with this downloads does not create any problem.
When building your kernel, which linux-libc-headers provider are you using?
Have you ensured that you did a "-c fetchall" for the image you want to
build so that all the downloads are sure to have downloaded before you
switch to no network?
Note that linux-libc-headers-yocto is the default linux-libc-headers
provider, and it uses the 2.6.37 yocto recipe, so it will need to
download that repository as well.
--
Darren
>
> On Tue, Sep 27, 2011 at 9:58 AM, Darren Hart <dvhart@linux.intel.com
> <mailto:dvhart@linux.intel.com>> wrote:
>
>
>
> On 09/16/2011 05:38 AM, chinmaya hoshing wrote:
> > Hi ,
> >
> > I am building poky-build minimal live image for fishriver machine
> on 64
> > bit host machine.
> > As I am having limited internet band-width, so I have identified
> all the
> > dependent packages and setup a Apache server on my local system so
> that
> > I can redirect the SRC_URI of all the packages to my local server.
> > I have changed the related recipes to build minimal live image, and
> > modify bitbake.conf to add LOCAL_MIRROR="xxx.xxx.xxx.xxx/packages"
> , in
> > side packages I have tars which was present "build/download" folder.
>
> OK... why not just use a common download directory? From what you've
> described your just trying to speed up the build on a single build
> system.
>
> --
> Darren
>
> >
> > While building linux-yocto, fetch and unpack was done but during
> kernel
> > checkout whatever git commits I have done previously in poky
> source were
> > flashed out (lost), also the only recipe remains in
> > meta/recipe-kernel/ is linux .
> >
> >
> > Following are the changes made in
> > meta/recipes-kernel/linux/linux-yocto_git.bb
> <http://linux-yocto_git.bb> <http://linux-yocto_git.bb>
> > #SRCREV_FORMAT = "meta_machine"
> > SRC_URI = "${LOCAL_MIRROR}/linux-yocto-3.0-3.0.tar.bz2"
> > // This tar file I took from
> >
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/snapshot/linux-yocto-3.0-3.0.tar.bz2
> > PV = "${LINUX_VERSION}"
> >
> > In file meta-intel/meta-fishriver/conf/machine/fishriver.conf I
> modified
> > PREFERRED_VERSION_linux-yocto = "3.0" (which was
> > PREFERRED_VERSION_linux-yocto = "3.0+git%" )
> >
> >
> > Can any one help me to find the solution that if I had to pull linux
> > kernel source from tar file or such and not from git repository. What
> > things I have to do.
> >
> > Regards
> > C Hoshing
> >
> >
> >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/poky
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2011-10-03 15:39 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-16 12:38 Getting error in linux-yocto kernel during build chinmaya hoshing
2011-09-16 14:24 ` Bruce Ashfield
2011-09-16 14:35 ` Bruce Ashfield
2011-09-16 15:06 ` Richard Purdie
2011-09-16 15:11 ` Bruce Ashfield
2011-09-16 15:22 ` Gary Thomas
2011-09-20 9:51 ` chinmaya hoshing
2011-09-20 13:54 ` Bruce Ashfield
2011-09-21 4:49 ` chinmaya hoshing
2011-09-21 12:30 ` Bruce Ashfield
2011-09-21 14:03 ` chinmaya hoshing
2011-09-21 16:10 ` Bruce Ashfield
2011-09-22 8:39 ` chinmaya hoshing
2011-09-22 14:50 ` Bruce Ashfield
2011-09-27 4:40 ` Darren Hart
2011-09-27 4:28 ` Darren Hart
2011-10-03 4:54 ` chinmaya hoshing
2011-10-03 15:39 ` Darren Hart
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.