Richard/Saul,

Here's the update for the sugarbay and beagleboard BSPs. To make the sugarbay
inhert common-pc-64 generic config/changes/fixes it has been
branched in the kernel as yocto/standard/common-pc-64/sugarbar, as
a result, we'll bump the common-pc-64 to be yocto/standard/common-pc-64/base.

I've built the common-pc-64, sugarbay and beagleboard here. Branch
renames and creations have been pushed to the repos.

This commit also stages lttng for a single board qemux86, but more
will follow by the end of day.

cc'ing Tom and Darren, since they both have changes pending on this
making it into the tree.

cc: Darren Hart <dvhart@...>
cc: Tom Zanussi <tom.zanussi@...>

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/bsp
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/bsp

Thanks,
Bruce Ashfield <bruce.ashfield@...>
---


Bruce Ashfield (1):
linux-yocto: BSP updates

.../conf/distro/include/poky-default-revisions.inc | 24 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_git.bb | 2 +-
2 files changed, 13 insertions(+), 13 deletions(-)

On 02/02/2011 06:45 AM, Gary Thomas wrote:

On 01/31/2011 05:41 PM, Kamble, Nitin A wrote:

Diego,

Can you try with 4.5.2 gcc from this branch: http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=nitin/khem_gcc_nitin

I too am having trouble (OMAP-L138 == armv5te/arm926ejs)

Nitin, I tried using your branch, but it failed to build:

NOTE: package gcc-cross-intermediate-4.5.2-r3: task do_populate_sysroot: Started
ERROR: Error executing a python function in /home/local/poky-contrib/meta/recipes-devtools/gcc/gcc-cross-intermediate_4.5.2.bb:
OSError: [Errno 2] No such file or directory:
'/home/local/efacec_omap_4.5.2/tmp/work/armv5te-poky-linux-gnueabi/gcc-cross-intermediate-4.5.2-r3/sysroot-destdir///home/local/efacec_omap_4.5.2/tmp/sysroots/cobra-omapl138p78//lib'

ERROR: The stack trace of python calls that resulted in this exception/failure was:
ERROR: File "sstate_task_postfunc", line 10, in <module>
ERROR:
ERROR: File "sstate_task_postfunc", line 4, in sstate_task_postfunc
ERROR:
ERROR: File "sstate.bbclass", line 17, in sstate_install
ERROR:
ERROR: File "/home/local/poky-contrib/meta/lib/oe/path.py", line 56, in copytree
ERROR: names = os.listdir(src)
ERROR:
ERROR: The code that was being executed was:
ERROR: 0006: bb.build.exec_func(intercept, d)
ERROR: 0007: sstate_package(shared_state, d)
ERROR: 0008:
ERROR: 0009:
ERROR: *** 0010:sstate_task_postfunc(d)
ERROR: 0011:
ERROR: (file: 'sstate_task_postfunc', lineno: 10, function: <module>)
ERROR: 0001:
ERROR: 0002:def sstate_task_postfunc(d):
ERROR: 0003: shared_state = sstate_state_fromvars(d)
ERROR: *** 0004: sstate_install(shared_state, d)
ERROR: 0005: for intercept in shared_state['interceptfuncs']:
ERROR: 0006: bb.build.exec_func(intercept, d)
ERROR: 0007: sstate_package(shared_state, d)
ERROR: 0008:
ERROR: (file: 'sstate_task_postfunc', lineno: 4, function: sstate_task_postfunc)
ERROR: Function 'sstate_task_postfunc' failed


Any ideas how to fix this?

Just to check, I applied the patches from Nitin's contrib tree
to poky/master and rebuilt - same results. I used the sequence
5b7e96d852778f1164198040cbd165241ea51e40..HEAD

*From:*yocto-bounces@... [mailto:yocto-bounces@...] *On Behalf Of *Diego Sueiro
*Sent:* Monday, January 31, 2011 10:53 AM
*To:* yocto@...
*Subject:* [yocto] Kernel Panics on armv4t with gcc.4.5.1

Folks,

I'm not a kernel and neither a gcc expert developer, and after searching for a solution for the last 2 weeks I've decided to appeal to the list.

I'm trying to build a kernel image (2.6.32 and 2.6.30) for mini2440 (armv4t) with Yocto Project (poky master branch) and I'm facing a strange issue.

If I compile the kernel with Yocto gcc recipes (gcc 4.5.1) the kernel will panic on init (console printed message is attached for kernel 2.6.30 and 2.6.32).

But, if I compile the kernel with meta-oe gcc recipes (gcc 4.5) everything will be ok.

Just for your reference these is the gcc recipes which I'm using:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gcc

http://git.openembedded.org/cgit.cgi/meta-openembedded/tree/recipes-devtools/gcc

I've compiled with and without thumb instructions, but the issue remains.

I've tried to apply the patches gcc-armv4-pass-fix-v4bx-to-ld.patch and gcc-arm-volatile-bitfield-fix.patch, but no success.

Kind Regards,

--

*dS
Diego Sueiro

/*long live rock 'n roll*/



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

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------

On 01/31/2011 05:41 PM, Kamble, Nitin A wrote:

Diego,

Can you try with 4.5.2 gcc from this branch: http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/log/?h=nitin/khem_gcc_nitin

I too am having trouble (OMAP-L138 == armv5te/arm926ejs)

Nitin, I tried using your branch, but it failed to build:

NOTE: package gcc-cross-intermediate-4.5.2-r3: task do_populate_sysroot: Started
ERROR: Error executing a python function in /home/local/poky-contrib/meta/recipes-devtools/gcc/gcc-cross-intermediate_4.5.2.bb:
OSError: [Errno 2] No such file or directory: '/home/local/efacec_omap_4.5.2/tmp/work/armv5te-poky-linux-gnueabi/gcc-cross-intermediate-4.5.2-r3/sysroot-destdir///home/local/efacec_omap_4.5.2/tmp/sysroots/cobra-omapl138p78//lib'

ERROR: The stack trace of python calls that resulted in this exception/failure was:
ERROR: File "sstate_task_postfunc", line 10, in <module>
ERROR:
ERROR: File "sstate_task_postfunc", line 4, in sstate_task_postfunc
ERROR:
ERROR: File "sstate.bbclass", line 17, in sstate_install
ERROR:
ERROR: File "/home/local/poky-contrib/meta/lib/oe/path.py", line 56, in copytree
ERROR: names = os.listdir(src)
ERROR:
ERROR: The code that was being executed was:
ERROR: 0006: bb.build.exec_func(intercept, d)
ERROR: 0007: sstate_package(shared_state, d)
ERROR: 0008:
ERROR: 0009:
ERROR: *** 0010:sstate_task_postfunc(d)
ERROR: 0011:
ERROR: (file: 'sstate_task_postfunc', lineno: 10, function: <module>)
ERROR: 0001:
ERROR: 0002:def sstate_task_postfunc(d):
ERROR: 0003: shared_state = sstate_state_fromvars(d)
ERROR: *** 0004: sstate_install(shared_state, d)
ERROR: 0005: for intercept in shared_state['interceptfuncs']:
ERROR: 0006: bb.build.exec_func(intercept, d)
ERROR: 0007: sstate_package(shared_state, d)
ERROR: 0008:
ERROR: (file: 'sstate_task_postfunc', lineno: 4, function: sstate_task_postfunc)
ERROR: Function 'sstate_task_postfunc' failed


Any ideas how to fix this?

*From:*yocto-bounces@... [mailto:yocto-bounces@...] *On Behalf Of *Diego Sueiro
*Sent:* Monday, January 31, 2011 10:53 AM
*To:* yocto@...
*Subject:* [yocto] Kernel Panics on armv4t with gcc.4.5.1

Folks,

I'm not a kernel and neither a gcc expert developer, and after searching for a solution for the last 2 weeks I've decided to appeal to the list.

I'm trying to build a kernel image (2.6.32 and 2.6.30) for mini2440 (armv4t) with Yocto Project (poky master branch) and I'm facing a strange issue.

If I compile the kernel with Yocto gcc recipes (gcc 4.5.1) the kernel will panic on init (console printed message is attached for kernel 2.6.30 and 2.6.32).

But, if I compile the kernel with meta-oe gcc recipes (gcc 4.5) everything will be ok.

Just for your reference these is the gcc recipes which I'm using:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gcc

http://git.openembedded.org/cgit.cgi/meta-openembedded/tree/recipes-devtools/gcc

I've compiled with and without thumb instructions, but the issue remains.

I've tried to apply the patches gcc-armv4-pass-fix-v4bx-to-ld.patch and gcc-arm-volatile-bitfield-fix.patch, but no success.

Kind Regards,

--

*dS
Diego Sueiro

/*long live rock 'n roll*/



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

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------

All,

I wanted to give everyone a heads up as we are coming up to the start of
the Yocto 1.0 release cycle. If you haven't had time to look at what the
next 2 months entail, please do so now at:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v._1.0_Release_Cycle

This Friday, February 4th, is our feature freeze date. We should be
mostly feature complete by then with pull requests made. Please have all
pull request for new features for 1.0 in by Friday if not earlier. Our
distro maintainers would appreciate not having a deluge of pull
requests, so, if possible, please have these in well before Friday
morning. The initial build of a release candidate will begin Friday @ 5pm.

The first stage of our release cycle will be a 3 week long cycle of
stabilizing master/bug fixing/QA with release candidate generation
occurring on February 25th-26th. During this time should also be doing
regular IRC bug scrubs as we did this morning.

Also, during the next two months I'll be sending out regular emails
about what should be expected for the coming week.

For the week of Feb 4th-10th:

Feb 4th: Feature Freeze
Initial Yocto Reference Manual is due to QA
Weekly Build

Feb 6th: Release Cycle Kickoff
Weekly Build finished and delivered for QA

Feb 8th: IRC Bug Scrub (#yocto)

Feb 10th: IRC Bug Scrub (#yocto)

Feb 11th: Weekly Build
Release Readiness Review


Thanks,

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer

On 02/01/2011 11:09 AM, Bruce Ashfield wrote:

On Tue, Feb 1, 2011 at 1:47 PM, Darren Hart<dvhart@...> wrote:

On 02/01/2011 09:25 AM, Bruce Ashfield wrote:

Fixes [BUGID #692]

Previously the information dumped by the kernel configuration audit
scripts was only placed in log files. This isn't as useful as it
could be, since they are rarely checked. This change takes the
output from kconf_check and explicitly displays it to the user.

Signed-off-by: Bruce Ashfield<bruce.ashfield@...>

diff --git a/meta/conf/distro/include/poky-default-revisions.inc
b/meta/conf/distro/include/poky-default-revisions.inc
index 0c3aa9a..ac0de6a 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc

-SRCREV_meta_pn-linux-yocto ?= "8a49ef6f1a43dabbce34a9ee9a1be08b26fc511c"
+SRCREV_meta_pn-linux-yocto ?= "e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99"

Was this an intentional change? It wasn't clear to me above which bits
necessitated a linux-yocto-2.6.37/meta SRCREV change.

Good catch, and typically that would have been a mistake. That's
me updating the captured scripts to have the updated kconf_check
(among others), so it was intentional, but I did for get to mention it
in the submission email.

Ah right, of course. Thanks!

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

On Tue, Feb 1, 2011 at 1:47 PM, Darren Hart <dvhart@...> wrote:

On 02/01/2011 09:25 AM, Bruce Ashfield wrote:

Fixes [BUGID #692]

Previously the information dumped by the kernel configuration audit
scripts was only placed in log files. This isn't as useful as it
could be, since they are rarely checked. This change takes the
output from kconf_check and explicitly displays it to the user.

Signed-off-by: Bruce Ashfield<bruce.ashfield@...>

diff --git a/meta/conf/distro/include/poky-default-revisions.inc
b/meta/conf/distro/include/poky-default-revisions.inc
index 0c3aa9a..ac0de6a 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc

-SRCREV_meta_pn-linux-yocto ?= "8a49ef6f1a43dabbce34a9ee9a1be08b26fc511c"
+SRCREV_meta_pn-linux-yocto ?= "e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99"

Was this an intentional change? It wasn't clear to me above which bits
necessitated a linux-yocto-2.6.37/meta SRCREV change.

Good catch, and typically that would have been a mistake. That's
me updating the captured scripts to have the updated kconf_check
(among others), so it was intentional, but I did for get to mention it
in the submission email.

Cheers,

Bruce

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
_______________________________________________
poky mailing list
poky@...
https://lists.yoctoproject.org/listinfo/poky

--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

On 02/01/2011 09:25 AM, Bruce Ashfield wrote:

Fixes [BUGID #692]

Previously the information dumped by the kernel configuration audit
scripts was only placed in log files. This isn't as useful as it
could be, since they are rarely checked. This change takes the
output from kconf_check and explicitly displays it to the user.

Signed-off-by: Bruce Ashfield<bruce.ashfield@...>

diff --git a/meta/conf/distro/include/poky-default-revisions.inc b/meta/conf/distro/include/poky-default-revisions.inc
index 0c3aa9a..ac0de6a 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc

-SRCREV_meta_pn-linux-yocto ?= "8a49ef6f1a43dabbce34a9ee9a1be08b26fc511c"
+SRCREV_meta_pn-linux-yocto ?= "e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99"

Was this an intentional change? It wasn't clear to me above which bits necessitated a linux-yocto-2.6.37/meta SRCREV change.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Fixes [BUGID #692]

Previously the information dumped by the kernel configuration audit
scripts was only placed in log files. This isn't as useful as it
could be, since they are rarely checked. This change takes the
output from kconf_check and explicitly displays it to the user.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta/classes/kernel-yocto.bbclass | 17 +++++++++++------
.../conf/distro/include/poky-default-revisions.inc | 4 ++--
meta/recipes-kernel/linux/linux-yocto.inc | 1 -
meta/recipes-kernel/linux/linux-yocto_git.bb | 1 +
4 files changed, 14 insertions(+), 9 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 8479b39..70521a4 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -131,17 +131,22 @@ do_kernel_configme() {
echo "ERROR. Could not configure ${KMACHINE}-${LINUX_KERNEL_TYPE}"
exit 1
fi
-
+
echo "# Global settings from linux recipe" >> ${B}/.config
echo "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
}

-do_kernel_configcheck() {
- echo "[INFO] validating kernel configuration"
- cd ${B}/..
- kconf_check ${B}/.config ${B} ${S} ${B} ${LINUX_VERSION} ${KMACHINE}-${LINUX_KERNEL_TYPE}
-}
+python do_kernel_configcheck() {
+ import bb, re, string, sys, commands

+ bb.plain("NOTE: validating kernel configuration")
+
+ pathprefix = "export PATH=%s; " % bb.data.getVar('PATH', d, True)
+ cmd = bb.data.expand("cd ${B}/..; kconf_check -${LINUX_KERNEL_TYPE}-config-${LINUX_VERSION} ${B} ${S} ${B} ${KBRANCH}",d )
+ ret, result = commands.getstatusoutput("%s%s" % (pathprefix, cmd))
+
+ bb.plain( "%s" % result )
+}

# Ensure that the branches (BSP and meta) are on the locatios specified by
# their SRCREV values. If they are NOT on the right commits, the branches
diff --git a/meta/conf/distro/include/poky-default-revisions.inc b/meta/conf/distro/include/poky-default-revisions.inc
index 0c3aa9a..ac0de6a 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc
@@ -57,7 +57,7 @@ SRCREV_pn-gypsy ??= "147"
SRCREV_pn-inputproto ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
SRCREV_pn-inputproto-native ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
SRCREV_pn-inputproto-nativesdk ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
-SRCREV_pn-kern-tools-native ??= "8832b75dc2e494ae96ca3e1dee7bfde2f3096904"
+SRCREV_pn-kern-tools-native ??= "fde7ef8fa8043607752563b9b7908f487eb2f7dd"
SRCREV_pn-libdrm ??= "3f3c5be6f908272199ccf53f108b1124bfe0a00e"
SRCREV_pn-libfakekey ??= "e8c2e412ea4a417afc1f30e32cb7bdc508b1dccc"
SRCREV_pn-libgdbus ??= "aeab6e3c0185b271ca343b439470491b99cc587f"
@@ -105,7 +105,7 @@ SRCREV_machine_pn-linux-yocto_atom-pc ?= "a9d833fda90e2f1257888a97e092135610b5f2
SRCREV_machine_pn-linux-yocto_routerstationpro ?= "219a5f9dc6e5beced36184e141f80b2df61ae32f"
SRCREV_machine_pn-linux-yocto_mpc8315e-rdb ?= "3f01b98238c2ff7913ce9f68f9db5ae9538717bc"
SRCREV_machine_pn-linux-yocto_beagleboard ?= "a9d833fda90e2f1257888a97e092135610b5f259"
-SRCREV_meta_pn-linux-yocto ?= "8a49ef6f1a43dabbce34a9ee9a1be08b26fc511c"
+SRCREV_meta_pn-linux-yocto ?= "e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99"
SRCREV_pn-linux-libc-headers-yocto ??= "a9d833fda90e2f1257888a97e092135610b5f259"
SRCREV_pn-matchbox-config-gtk ??= "3ed74dfb7c57be088a5ab36e446c0ccde9fa1028"
SRCREV_pn-matchbox-desktop-sato ??= "76"
diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index dc4ab55..3ad849e 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -15,7 +15,6 @@ LINUX_KERNEL_TYPE ?= standard
do_patch[depends] = "kern-tools-native:do_populate_sysroot"

addtask kernel_configme before do_configure after do_patch
-addtask kernel_configcheck after do_configure before do_compile

# Pick up shared functions
inherit kernel-yocto
diff --git a/meta/recipes-kernel/linux/linux-yocto_git.bb b/meta/recipes-kernel/linux/linux-yocto_git.bb
index 7833f65..b1486bc 100644
--- a/meta/recipes-kernel/linux/linux-yocto_git.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_git.bb
@@ -30,5 +30,6 @@ KERNEL_FEATURES=features/netfilter
# 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
--
1.7.3.4

Fixes [BUGID #685]

Although not used if the in kernel uImage is booted, it is
a good idea to set the UBOOT_ENTRYPOINT just as the other
uImage based boards do.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta/conf/machine/mpc8315e-rdb.conf | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/meta/conf/machine/mpc8315e-rdb.conf b/meta/conf/machine/mpc8315e-rdb.conf
index e3f9d23..ac518fb 100644
--- a/meta/conf/machine/mpc8315e-rdb.conf
+++ b/meta/conf/machine/mpc8315e-rdb.conf
@@ -14,3 +14,6 @@ MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
+
+UBOOT_ENTRYPOINT = "0x00000000"
+
--
1.7.3.4

Richard/Saul,

I'm addressing a couple of bugs in this pull request.

Bug #685: for the mpc8315e-rdb boot issue. I'm going to revisit
this one, since changing the entry point shouldn't be making a
difference to this board's boot (by me looking at th code), but
it does seem to fix the problem according to the reporter.

Bug #692: kernel configuration audit information

After configuration of the kernel and audit is performed, and
has been for some time. This updates it to work with the 2.6.37
kernel and makes the output visible. You now get something like
this:

------------------------
NOTE: package linux-yocto-2.6.37+git0+e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99_0+a9d833fda90e2f1257888a97e092135610b5f259-r15: task do_kernel_configcheck: Started
NOTE: validating kernel configuration
The following Kconfig files no longer exist in this tree:
drivers/ieee1394/Kconfig
drivers/media/video/zc0301/Kconfig

This BSP sets 1 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your workspace at:
/home/bruce/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git0+e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99_0+a9d833fda90e2f1257888a97e092135610b5f259-r15/linux/meta/cfg/yocto/standard/common-pc/invalid.cfg

This BSP sets 6 kernel options that are possibly non-hardware related.
The full list can be found in your workspace at:
/home/bruce/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git0+e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99_0+a9d833fda90e2f1257888a97e092135610b5f259-r15/linux/meta/cfg/yocto/standard/common-pc/specified_non_hdw.cfg

WARNING: There were 2 hardware options requested that do not
have a corresponding value present in the final ".config" file.
This probably means you aren't getting the config you wanted.
The full list can be found in your workspace at:
/home/bruce/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git0+e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99_0+a9d833fda90e2f1257888a97e092135610b5f259-r15/linux/meta/cfg/yocto/standard/common-pc/mismatch.cfg

Waiting a second to make sure you get a chance to see this...
NOTE: package linux-yocto-2.6.37+git0+e8b8c1ae44932835f4f79e77180d3ce5e4b1ec99_0+a9d833fda90e2f1257888a97e092135610b5f259-r15: task do_kernel_configcheck: Succeeded
------------------------

This is actually telling us something useful, and actually is showing
me something that need to be fixed in the Kconfig classification for
2.6.37 .. so it has already proven to be useful data to expose
to the user!


Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Thanks,
Bruce Ashfield <bruce.ashfield@...>
---


Bruce Ashfield (2):
mpc8315e-rdb: set UBOOT_ENTRYPOINT
linux-yocto: export kernel configuration audit to the console

meta/classes/kernel-yocto.bbclass | 17 +++++++++++------
.../conf/distro/include/poky-default-revisions.inc | 4 ++--
meta/conf/machine/mpc8315e-rdb.conf | 3 +++
meta/recipes-kernel/linux/linux-yocto.inc | 1 -
meta/recipes-kernel/linux/linux-yocto_git.bb | 1 +
5 files changed, 17 insertions(+), 9 deletions(-)

--
1.7.3.4

Nitin,

echo "/* GNU ld script

   Use the shared library, but some functions are only in

   the static library.  */

GROUP ( libgcc_s.so.1 libgcc.a )" > ${D}${libdir}/libgcc_s.so

Nitin,

Hi,

In my own task named 'task-via-sdk.bb', I put gcov and gcov-symbolic.
My target is to generate an image with SDK tools with gcov. We use
gcov as coverage tools.

This task runs OK but when the task do_rootfs will run, it does not
find gcov-symbolic.

I make a grep on meta/, but nobody use gcov. The package is defined
on recipes-devtools/gcc/gcc-package-target.inc

My question is: Somebody uses gcov with yocto images?

Thanks.

--
-----------------------------------------------------------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br

Folks,

I'm not a kernel and neither a gcc expert developer, and after searching for a solution for the last 2 weeks I've decided to appeal to the list.

I'm trying to build a kernel image (2.6.32 and 2.6.30) for mini2440 (armv4t) with Yocto Project (poky master branch) and I'm facing a strange issue.

If I compile the kernel with Yocto gcc recipes (gcc 4.5.1) the kernel will panic on init (console printed message is attached for kernel 2.6.30 and 2.6.32).

But, if I compile the kernel with meta-oe gcc recipes (gcc 4.5) everything will be ok.

Just for your reference these is the gcc recipes which I'm using:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gcc

http://git.openembedded.org/cgit.cgi/meta-openembedded/tree/recipes-devtools/gcc

I've compiled with and without thumb instructions, but the issue remains.

I've tried to apply the patches gcc-armv4-pass-fix-v4bx-to-ld.patch and gcc-arm-volatile-bitfield-fix.patch, but no success.

Kind Regards,

*dS
Diego Sueiro

/*long live rock 'n roll*/

Hi all,
This is latest Yocto bug trend chart. Open bug number increased from 172 to 182 last week. There remain 22 "Undecided" bugs now.

Best Regards,
Jiajun

Saul Wold wrote:

Folks,

Please find attached the list of M3 Recipe Updates, our goal for 1.0
M3 release is to complete the update process we started in 0.9 and
1.0 M2. There are about 150 recipes in this list, some people may
have more and if there is a need to request help, please let me know.
If you plan on helping, please let the current owner know that you
will be updating a recipe.

Unless I hear otherwise, I will work to update the "None" maintained
list, but I believe some of these are owned by people and the distro
tracking information needs to be updated.

Thanks again to the team for the hard work during 0.9 and M2, we will
always have updates to do, but they will get easier with our gained
experience and expertise.

Happy Holidays and Happy New Year to all.

Hi Saul,
Here is the update for recipes in the list with me as the owner:

There are 18 recipes in total:
1) I have upgraded 14 ones:
renderproto
inputproto
libdmx
lttng-viewer
liburcu
libxxf86misc
compositeproto
resourceproto
xproto
gnome-doc-utils
scrnsaverproto
lttng-ust
librsvg
pixman: upgraded from 0.20.0 to 0.21.2 and later downgraded to 0.20.2 since 0.21.x is development release.

2) I decided to not upgrade these 2 ones and upgraded RECIPE_NO_UPDATE_REASON:
libunique: Do not upgrade to version: 2.91.4 because it requires gtk+ >= 2.90.0 and the stable version of gtk+ used by poky is 2.2x.x
liberation-fonts: Do not upgrade to version: 1.06.0.20100721 because before doing that, we need adding new native packages like libungif_4.1.3, libspiro and fontforge first

3) These 2 ones doesn't need upgrade at present:
lttng-control: acutally not newer release is available. The script detecting new release thought 0.88-09242010 are different from 0.88. Mei Lei has fixed that.
tcf-agent: as Lianhao said, the upstream is re-orging the code, so we can only wait for now. Previously the script detecting new release simply printed a useless svn number "998".

Thanks,
-- Dexuan

Op 30 jan 2011, om 10:56 heeft Frans Meulenbroeks het volgende geschreven:

2011/1/30 Koen Kooi <koen@...>:

FWIW, there's also a cleaned-up cups in meta-oe

It is not that clean as it has QA issues.

The cups in meta-oe is 1.4.x, you are posting 1.2.x QA errors.

I posted the message below a few days ago to the OE mailing list.
I've not too much knowledge on .desktop files, so I have no idea how to fix it.

Frans.

--- forwarded message

Hi,

I got this while building cups, but I am not a gnome person (actually
I am only intterested in the server part).

ERROR: QA Issue with cups:
/home/hudson/jobs/FM_TEST/workspace/tmp/work/ppce500v2-oe-linux-gnuspe/cups-1.2.12-r7.2/packages-split/cups/usr/share/applications/cups.desktop:
warning: value "Application;System;X-Red-Hat-Base;" for key
"Categories" in group "Desktop Entry" contains a deprecated value
"Application"
ERROR: QA Issue with cups:
/home/hudson/jobs/FM_TEST/workspace/tmp/work/ppce500v2-oe-linux-gnuspe/cups-1.2.12-r7.2/packages-split/cups/usr/share/applications/cups.desktop:
warning: key "Encoding" in group "Desktop Entry" is deprecated
ERROR: QA Issue with cups:
/home/hudson/jobs/FM_TEST/workspace/tmp/work/ppce500v2-oe-linux-gnuspe/cups-1.2.12-r7.2/packages-split/cups/usr/share/applications/cups.desktop:
warning: value "" for key "Path" in group "Desktop Entry" does not
look like an absolute path
ERROR: QA Issue with cups:
/home/hudson/jobs/FM_TEST/workspace/tmp/work/ppce500v2-oe-linux-gnuspe/cups-1.2.12-r7.2/packages-split/cups/usr/share/applications/cups.desktop:
warning: key "TerminalOptions" in group "Desktop Entry" is deprecated

Anyone care to fix this or provide a suggestion on how to fix ?

Thanks, Frans

On 01/28/2011 12:31 AM, Chris Tapp wrote:

I'm getting a QA failure when running a build from a recent git master:

Checking autotools environment for common misconfiguration
NOTE: Checking autotools environment for common misconfiguration
linux: Recipe file does not have license file information
(LIC_FILES_CHKSUM)
ERROR: linux: Recipe file does not have license file information
(LIC_FILES_CHKSUM)
Licensing Error: LIC_FILES_CHKSUM does not match, please fix
ERROR: Licensing Error: LIC_FILES_CHKSUM does not match, please fix
Function 'do_qa_configure' failed
ERROR: Function 'do_qa_configure' failed

This is when building kernel version 2.6.33.2-r2.

Chris,

This has been fixed in master, this is due to that recipe missing the LIC_FILES_CHKSUM (as noted in the error message). I added the missing line:

+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"

Thanks for pointing this one out.


Sau!

Chris Tapp

opensource@...
www.keylevel.com



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

Hi all,
The next table is for the latest lsb test result.

LSB Test Suite	Version	Result	Left work	May/Days	Start Date	Finish Date	Status	Completed Percentage	Defects filed	Developer	Risk/Issue
Cpp-T2C Tests	4.0.2-1	Passed	submit	2	2010-12-20	2010-12-21	In Progress	90%		Jingdong Lu
Libstdc++ Tests	4.1.0-7	Passed	submit	3	2010-12-22	2010-12-24	In Progress	90%		Jingdong Lu
Perl Tests	4.0.7-1	Passed	None	2	2010-12-27	2010-12-28	Done	100%		Jingdong Lu
Python Runtime Tests	4.0.2-1	Passed	submit	3	2010-12-29	2010-12-31	In Progress	90%	Bug 614(Open)	Jingdong Lu
Python Tests	2.4.5-2	Passed	submit	0			In Progress	90%		Jingdong Lu
OLVER Core Tests		Passed	submit	6	2011-1-4	2011-1-11	In Progress	90%		Jingdong Lu
Command Check	4.0.0-2	Passed	Lsb	3	2011-1-12	2011-1-14	In Progress	90%	BUG 520(Closed)	Jingdong Lu
Tcl Tests	8.5.7-6	Passed	None	5	2011-1-17	2011-1-21	Done	100%		Jingdong Lu
Library Check	4.0.2-1	Failures: 2	qt3	5	2011-1-12	2011-1-18	In Progress	80%		Jingdong Lu	Query if we need to handle any QT3 issues
Desktop Tests		Passed	submit	4	2010-12-20	2010-12-29	In Progress	90%	BUG 567(Closed) BUG 569(Closed) BUG 570(Closed)	Xiaofeng Yan
Desktop-T2C Tests	4.0.2-1	Failures: 1	Lsb test suite	4	2010-12-20	2010-12-29	Block	90%	BUG 571(Accepted)	Xiaofeng Yan	Test suite led to these failed items. http://bugs.linuxbase.org/show_bug.cgi?id=3153
Qt4-Azov Tests	4.0.2-1	Failures:3	Lsb test suite	4	2010-12-30	2011-1-5	Block	90%		Xiaofeng Yan	Test suite led to these failed items. (Qlocale) http://bugs.linuxbase.org/show_bug.cgi?id=3125 (QmenBar) http://bugs.linuxbase.org/show_bug.cgi?id=3124 Http://bugs.linuxbase.org/show_bug.cgi?id=3067
Xts5 Tests	5.1.5-19	Passed	submit	5	2011-1-6	2010-1-12	In Progress	90%		Xiaofeng Yan
Core Tests	4.0.5-1	Failures: 25	fix failures	5	2011-1-19	2011-1-25	Delay	50%		Xiaofeng Yan	Test suite led to these failed items. T.c_iflag http://bugs.linuxbase.org/show_bug.cgi?id=3033 T.tcgetattr http://bugs.linuxbase.org/show_bug.cgi?id=3033 http://bugs.linuxbase.org/show_bug.cgi?id=2071
Qt3-Azov Tests	4				N/A	N/A	Not Start Yet			N/A
LSB Test Suite			creat-lsb-image LSB_Setup.sh	0			Done	100%		Xiaofeng Yan
X86_32 LSB Finish Date	2011-2-11
Re-test on X86_64 & ppc Finish Date	2011-3-11
Yocto M3 Stabilize Finish Date	2011-2-11
Tested on: (self built LSB image)