Re: [yocto] [PATCH][meta-virtualization] openvsitch: set CONFIGUREOPT_DEPTRACK to empty

2015-08-26 Thread Bruce Ashfield

On 15-08-26 01:48 AM, rongqing...@windriver.com wrote:

From: Roy Li 

compilation failed since the needed dirs maybe not created when make
".in" target, fix it by creating the needed dirs before, but mainstream
thinks the needed dirs should be created when do configuration.
at last, find CONFIGUREOPT_DEPTRACK disable the creation, so empty
it
http://openvswitch.org/pipermail/dev/2015-August/059189.html

set CONFIGUREOPT_DEPTRACK to empty, is lower effective, but harmless,
and can fix the parallel building issue;
see oe-core 970e0ae6108[autotools: Disable dependency tracking


This should have gone to the meta-virtualization mailing list, but no
need to re-send .. I have it from here and have merged it.

Bruce



Signed-off-by: Roy Li 
---
  recipes-networking/openvswitch/openvswitch.inc | 1 +
  1 file changed, 1 insertion(+)

diff --git a/recipes-networking/openvswitch/openvswitch.inc 
b/recipes-networking/openvswitch/openvswitch.inc
index 58c8352..454aadf 100644
--- a/recipes-networking/openvswitch/openvswitch.inc
+++ b/recipes-networking/openvswitch/openvswitch.inc
@@ -39,6 +39,7 @@ EXTRA_OECONF += "\
TARGET_PYTHON=${bindir}/python \
TARGET_PERL=${bindir}/perl \
"
+CONFIGUREOPT_DEPTRACK = ""

  # Don't compile kernel modules by default since it heavily depends on
  # kernel version. Use the in-kernel module for now.



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] How to recreate rootfs image

2015-08-26 Thread Lenivyy Viktor
Hello.
I have “altera-image-minimal” recipe which creates minimal rootfs based on 
Linux kernel provided by “linux-altera-local” recipe. This kernel is fetched 
from local directory.
After first time building “altera-image-minimal”, it produced rootfs with 
modules version contained “-dirty” at the end. However kernel built from 
sources in local directory doesn’t have “-dirty” in version string. Thus kernel 
can’t run with produced rootfs.
I opened directory which contains Yocto’s copy of Linux sources
build/tmp/work/socfpga_socrates-poky-linux-gnueabi/linux-altera-local-1.0-r1/socrates_linux/
then run “make ARCH=arm kernelrelease” to investigate kernel version. This 
command outputs the version with “-dirty”. I have found that “-dirty” string is 
appended from script in kernel sources. That script uses output from “git 
diff-index --name-only HEAD” to determine if working directory is “dirty”. To 
find changed files, I ran same command, it’s oddly but the output was empty. 
Then I rerun “make ARCH=arm kernelrelease”. This time it prints  the version 
without “-dirty”.
Does someone have any clue why it can be so?

My main question is: how can I recreate rootfs image starting from the point 
after fetching Linux sources, so Yocto’s copy will remain intact?

I spent lot of time trying to figure it out by myself with no luck. My idea was 
to find sequence of commands used to create image and run only commands after 
fetching kernel sources. Unfortunately I didn’t manage to find the sequence 
anywhere. How such things need to be solved in Yocto?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] How to recreate rootfs image

2015-08-26 Thread Nikolay Dimitrov

Hi Lenivyy Viktor,

On 08/26/2015 05:37 PM, Lenivyy Viktor wrote:

Hello.

I have “altera-image-minimal” recipe which creates minimal rootfs based
on Linux kernel provided by “linux-altera-local” recipe. This kernel is
fetched from local directory.

After first time building “altera-image-minimal”, it produced rootfs
with modules version contained “-dirty” at the end. However kernel built
from sources in local directory doesn’t have “-dirty” in version string.
Thus kernel can’t run with produced rootfs.

I opened directory which contains Yocto’s copy of Linux sources

build/tmp/work/socfpga_socrates-poky-linux-gnueabi/linux-altera-local-1.0-r1/socrates_linux/

then run “make ARCH=arm kernelrelease” to investigate kernel version.
This command outputs the version with “-dirty”. I have found that
“-dirty” string is appended from script in kernel sources. That script
uses output from “git diff-index --name-only HEAD” to determine if
working directory is “dirty”. To find changed files, I ran same command,
it’s oddly but the output was empty. Then I rerun “make ARCH=arm
kernelrelease”. This time it prints  the version without “-dirty”.

Does someone have any clue why it can be so?

My main question is: how can I recreate rootfs image starting from the
point after fetching Linux sources, so Yocto’s copy will remain intact?

I spent lot of time trying to figure it out by myself with no luck. My
idea was to find sequence of commands used to create image and run only
commands after fetching kernel sources. Unfortunately I didn’t manage to
find the sequence anywhere. How such things need to be solved in Yocto?



Can you please try this and share if it works for you:

bitbake -c cleanall dirtypackage myimage
bitbake myimage

Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] How to recreate rootfs image

2015-08-26 Thread Lenivyy Viktor
> Can you please try this and share if it works for you:
>
> bitbake -c cleanall dirtypackage myimage
> bitbake myimage
>
> Regards,
> Nikolay

What is dirtypackage? Myimage will be altera-image-minimal in my case, I guess.
I’m wondering whether cleanall doesn’t remove Yocto’s copy of kernel sources?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] How to recreate rootfs image

2015-08-26 Thread Nikolay Dimitrov

Hi Lenivyy Viktor,

On 08/26/2015 06:42 PM, Lenivyy Viktor wrote:

 Can you please try this and share if it works for you:







 bitbake -c cleanall dirtypackage myimage



 bitbake myimage







 Regards,



 Nikolay


What is dirtypackage? Myimagewill be altera-image-minimal in my case, I
guess.

I’m wondering whether cleanall doesn’t remove Yocto’s copy of kernel
sources?



dirtypackage is the one which you want to rebuild and redeploy in the
rootfs. If the package source is local, cleanall won't do big harm, but
otherwise you're correct, it will clean the sources. You can use
"clean" instead.

Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] How to recreate rootfs image

2015-08-26 Thread Lenivyy Viktor
> dirtypackage is the one which you want to rebuild and redeploy in the
> rootfs. If the package source is local, cleanall won't do big harm, but
> otherwise you're correct, it will clean the sources. You can use
> "clean" instead.

> Regards,
> Nikolay

I don’t know exactly which package I need to rebuild, but I guess it’s 
kernel-modules as modules folder have wrong version.
After
bitbake -c clean kernel-modules altera-image-minimal

there is an error:
…
ERROR: Nothing PROVIDES 'kernel-modules'
…




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] How to recreate rootfs image

2015-08-26 Thread Khem Raj
On Wed, Aug 26, 2015 at 9:13 AM, Lenivyy Viktor
 wrote:
>> dirtypackage is the one which you want to rebuild and redeploy in the
>
>> rootfs. If the package source is local, cleanall won't do big harm, but
>
>> otherwise you're correct, it will clean the sources. You can use
>
>> "clean" instead.
>
>
>
>> Regards,
>
>> Nikolay
>
>
>
> I don’t know exactly which package I need to rebuild, but I guess it’s
> kernel-modules as modules folder have wrong version.
>
> After
>
> bitbake -c clean kernel-modules altera-image-minimal
>
>
>
> there is an error:
>
> …
>
> ERROR: Nothing PROVIDES 'kernel-modules'

kernel modules are part of virtual/kernel so you need to clean
virtual/kernel if thats what the issue is

>
> …
>
>
>
>
>
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] FW: How to recreate rootfs image

2015-08-26 Thread Lenivyy Viktor
> >> dirtypackage is the one which you want to rebuild and redeploy in the
> >
> >> rootfs. If the package source is local, cleanall won't do big harm,
> >> but
> >
> >> otherwise you're correct, it will clean the sources. You can use
> >
> >> "clean" instead.
> >
> >
> >> Regards,
> >
> >> Nikolay
> >
> >
> > I don’t know exactly which package I need to rebuild, but I guess it’s
> > kernel-modules as modules folder have wrong version.
> >
> > After
> >
> > bitbake -c clean kernel-modules altera-image-minimal
> >
> >
> > there is an error:
> >
> > …
> >
> > ERROR: Nothing PROVIDES 'kernel-modules'
> 
> kernel modules are part of virtual/kernel so you need to clean virtual/kernel
> if thats what the issue is

This command did what I was trying to avoid: remove Yocto's copy of kernel 
sources. But starting questions still exist.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] FW: How to recreate rootfs image

2015-08-26 Thread Nikolay Dimitrov

Hi Victor,

On 08/26/2015 08:12 PM, Lenivyy Viktor wrote:

This command did what I was trying to avoid: remove Yocto's copy of kernel 
sources. But starting questions still exist.



In your kernel recipe are you using SRC_URI to fetch from a git
repository (e.g. git:// URI) or from a local directory?

I guess that if you're using a local path, there can be either some
uncommitted changes, or a stale git index.

You can try just for the experiment to add your current kernel sources
to a test git repo and point the SRC_URI to it, so bitbake can clone
the repo by git revision (SRCREV = "${AUTOREV}" will skip the need to
update the recipe revision constantly during development). This should
work fine, without the "-dirty" version suffix.

Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto