Thanks Nitin,

That fixed my automake errors.

- Josef

Attendees:
Beth, Scott, Dave, Darren, Tom, Richard, Matthew, Mark, Denys, Paul, Belen, Saul, Josh, Jeff, Michael, Jessica, Bruce, Song
 
Agenda
 
* Opens collection - 5 min (Song)
* Yocto 1.1.1 point release update - 10 min (Josh/Beth)
- We have SSB approval
- working through doc example, running into an issue, working through it (new branch). Trying to have the build done for QA when they come back from CNY.
- Scott is looking for ADT installer to verify the example. Beth will get back to Scott for the ADT installer tarball.
* Yocto 1.2 M2 status - 10 min (Song/Team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status
- RC1 is out, QA has weekly test result. Looks good except the crownbay issue. Having an issue trying to get FRI II build. Crownbay fix will be pulled into RC2. Crownbay issue is fixed last week. Nitin's patches will fix FRI II.
- Package update has met our target.
- Bug fixing: no high bugs outstanding now. Have a little more bugs but the total number of medium+ bugs are still under control.

* Opens - 10 min 
- Song: Status to indicate the feature is in master: Developers should put the feature bug into 'fixed' state when the patch is in master. Darren has a place to check logs for feature status.
- Scott Rifenbark: 1.1.1 ADT installer tarball
-
* Action item Review - 5 min
- Paul to work with Jeremy and others to move 1598 forward. (Leave it in Bugzilla to track it)
 
* Team Sharing - 20 min
Bruce: generated 3.2 kernel tree, now doing final build and test. There will be 1.2 candidate tree shortly. RP: ask Bruce to keep an eye on autobuilder. There was a problem with compile perf. Check any non-qemu machine. Bruce will take a look. The candidate tree may need more time to be ready.
Jessica: some 1.3 planning work. Waiting for tom's bsp kernel tool for M3 delivery.
Michael: Bad networking problem, fixed last week. working on setting on home office, some DNS fix for yocto.org, virtualization for eglibc, setting up servers for LF. This week upgrading Bugzilla, eglibc. Some hardware issue, but not really blockers, can work around it.
Jeff: nothing
Josh: working on stable release.
Saul: working with consolidated pulls, looking at M3 planning.
Belen: reviewing the UI implementation for 1.2, managing to get some visual done, not much time for Yocto, should be cleared in the next few days
Paul: working on error handling on bitbake, put in some of the fixes. Trying to get a lot annoyance and unhelpful messages. Please make Paul and Richard aware of the issue if you see any problem in this area. Will work on the build history. Encouraging people to file in bugzilla for any unhelpful error messages. This effort will be ongoing.
Denys:no
Mark: got permission from management for a public SE Linux layer. In a couple of days to get basic support. Tired of doing it ourselves. We put it out there, worst case we are still doing it on our own. This is not official announcement.
Matthew: testing 1.1.1, looks pretty good, just one issue. Will talk to Josh. Michael/Saul will add 1.1.1 version target in Bugzilla.
Richard: review patches, error handling, will work on bugs, get help for some other bugs.
Tom: worked on license, BSP and kernel tools, template engine working, next step is to put on the command line interface. By the beginning of M3, we should have something for Jessica. Will be working on kernel tools.
Darren: is there anyone who is interested in small distribution. Please look at pokyy-tiny, would like to get more feedback. If anyone interested in EFI, please send email to Darren,
Scott: verified 1.1.1 examples, except the ADT mannul. Created a paragraph for ScottG's virtual machine. In the coming week, finish the ADT manual for 1.1.1, get back on to some bugs. Only thing blocking is the installer.
Beth: worked on some license stuff, autobuilder layering, want to test out this Friday, may have some autobuilder downtime for testing this Friday.
Nitin: Sent a fix to Darren for FRI II problem, starting to look into gcc multi-lib, gdk recipe, etc.

On 17/01/12 13:46, Flanagan, Elizabeth wrote:

All,

The autobuilder infrastructure will be unavailable for part of the
day, Friday January 20th between 9am to 4pm. I will be adding some

PST, I assume? i.e. UTC-8

Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre

All,

The autobuilder infrastructure will be unavailable for part of the
day, Friday January 20th between 9am to 4pm. I will be adding some
additional buildset targets. During this time, build failure emails
will be disabled. This will not effect any of the other services
hosted by the autobuilder infrastructure (source mirror, etc)

Thanks.

--
Elizabeth Flanagan
Yocto Project
Build and Release

On Tue, 2012-01-17 at 11:17 -0800, Joshua Lock wrote:

On 10/01/12 11:54, Tom Zanussi wrote:

On Tue, 2012-01-10 at 09:39 -0800, Joshua Lock wrote:

CAVEAT: This series requires the alsa-state series recently submitted to the
OE-Core mailing list.

Nice. Thanks for finally resolving this. When the other patches hit
oe-core, I'll pull these in...

FYI the alsa-state recipe has hit master.

Boot-tested on n450 and pulled into meta-intel/master.

Thanks,

Tom

Joshua

On 10/01/12 11:54, Tom Zanussi wrote:

On Tue, 2012-01-10 at 09:39 -0800, Joshua Lock wrote:

CAVEAT: This series requires the alsa-state series recently submitted to the
OE-Core mailing list.

Nice. Thanks for finally resolving this. When the other patches hit
oe-core, I'll pull these in...

FYI the alsa-state recipe has hit master.

Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre

On 12-01-12 08:14 AM, Zhai, Edwin wrote:

Bruce,
Thanks for your efforts!

FYI: I haven't forgotten about this, I'm just reworking a few
things with the 3.2 kernel tree, and will include this as part
of that effort. It will all be available soon.

Bruce

Edwin

On 2012/1/11 20:43, Bruce Ashfield wrote:

On 12-01-11 02:01 AM, Zhai, Edwin wrote:

Bruce,
Can we enable SMP and virtio by default for qemux86/x86-64? This can
achieve
huge perf boost for workload inside qemu. E.g. we enabled self-hosted
image,
where we build yocto inside qemu.

Attached patch showes the kernel config option.

Is it reasonable?

It should be. I just need to look at the fallback modes, and how this
impacts different host systems. That being said, I've run with similar
configs in the past (depending on the workload) with no issues.

qemux8-64 is already SMP, so it would just need the addition of virtio
devices, which just means we'd look at this as any BSP/target config
update.

But with graceful degradation (i.e maxcpus with SMP set) and agreement
that we'd like to simulate SMP by default, then we can make the change
and I'll merge it into the base config for the target and pull it into
the kernel tree.

Cheers,

Bruce

Thanks,
Edwin

I get the same build ERRORS without meta-kernel-dev as well.

Thanks
Kishore.

I'm using a Marshalltown Cedarview board and it's serial ports are standard PC com1 and com2 so I put the following in my conf/machine/mycdv.conf file, where mycdv is the name of my machine/bsp, i.e. meta-mycdv.

SERIAL_CONSOLE = "115200 ttyS0"
SYSLINUX_OPTS = "serial 0 115200"
APPEND = "console=ttyS0,115200 console=tty0"

When the system booted, I have the kernel console on com1 and I also got a login prompt on com1. However, the syslinux output was only displayed on the VGA monitor.

Anyone know why? Maybe SYSLINUX_OPTS goes somewhere else?

I noticed in the n450 release notes that they accomplish this with the following in the local.conf file:

# Serial Port Setup for Intel Embedded Development Board 1-N40\
SYSLINUX_OPTS_atom-pc = "serial 0 115200"
SERIAL_CONSOLE_atom-pc = "115200 ttyS0"
APPEND_atom-pc = "console=ttyS0,115200 console=tty0"

This does work for the N450, but the cedartrail bsp is not under standard/common-pc/atom-pc. It's under standard/cedartrail. If I have to put SYSLINUX_OPTS in local.conf, what is the suffix and why???

JIm A

On 01/16/2012 02:00 PM, Kamble, Nitin A wrote:

Darren,
I have reworked the commits to fix issues while building on other distros.
Can you check this branch http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=nitin/grub-efi
It is working for me on Fedora 14, for which the other grub-efi commit was failing for me.

Thanks Nitin,

Builds fine for me on Ubuntu 11.10 64 bit

--
Darren

Thanks,
Nitin

-----Original Message-----
From: Kamble, Nitin A
Sent: Thursday, January 12, 2012 2:33 PM
To: Kamble, Nitin A; Hart, Darren; Bodke, Kishore K
Cc: Ahmad, Josef; yocto@...
Subject: RE: [yocto] qemu EFI build failure

Here is the commit: http://git.yoctoproject.org/cgit.cgi/poky-
contrib/log/?h=nitin/misc

Nitin

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-
bounces@...] On Behalf Of Kamble, Nitin A
Sent: Thursday, January 12, 2012 2:32 PM
To: Hart, Darren; Bodke, Kishore K
Cc: Ahmad, Josef; yocto@...
Subject: Re: [yocto] qemu EFI build failure


I just sent a patch to oecore mailing list to fix the grub issue with
automake 1.11.2.

Thanks,
Nitin

-----Original Message-----
From: Hart, Darren
Sent: Thursday, January 12, 2012 1:39 PM
To: Bodke, Kishore K
Cc: Ahmad, Josef; yocto@...; Kamble, Nitin A
Subject: Re: [yocto] qemu EFI build failure

On 01/12/2012 01:28 PM, Bodke, Kishore K wrote:

I have only
MACHINE_FEATURES += "efi"
KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc".

I am not having IMAGE_FSTYPES += "live".

The "live" change is just to trigger the live image type which

builds

grub-efi-native for efi systems. qemux86 needs this added

explicitly.

--
Darren

Thanks
Kishore.
-----Original Message-----
From: Hart, Darren
Sent: Thursday, January 12, 2012 1:20 PM
To: Ahmad, Josef
Cc: yocto@...; Bodke, Kishore K; Kamble, Nitin A
Subject: Re: [yocto] qemu EFI build failure

On 01/12/2012 10:27 AM, Darren Hart wrote:

On 01/12/2012 08:19 AM, Josef Ahmad wrote:

I tried to build a qemux86 EFI image, by setting:
- in my local.conf: IMAGE_FSTYPES += "live"
- in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES +=

"efi"

I haven't tried live images with QEMU. For one thing, they

aren't

really

necessary as you can specify all the boot parameters on the qemu

command

line. Is there are reason you want to use the live image

specifically?

Also, in order to properly test EFI in QEMU, you will need to

use

an

EFI

BIOS - I believe you're aware of this already - but this isn't

currently

supported by the runqemu scripts that ship with yocto.

The build gave me the following error:

I'll do some test builds - it isn't clear to me what is going on

here.

<snip>

Has anyone encountered the same error? I'm not sure I set up

the

correct configuration. Also, is there another way to append

"efi"

to

MACHINE_FEATURES rather than by modifying qemux86.conf?

You should be able to do something like:
MACHINE_FEATURES_append_qemux86 = "efi"

Note that you will also need to enable the efi support in the

kernel,

which is done with the KERNEL_FEATURES variable, something like:
KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"

Either of these can be set in your local.conf.

More accurately:

MACHINE_FEATURES_append_qemux86=" efi pcbios"
KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
IMAGE_FSTYPES += "live"

With these added to local.conf and building for qemux86 I see the

same

configure failures reported by Kishore and Josef:

| ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded

from...

| acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded

from...

I've discussed in IRC with Nitin and he thinks this may be

related

to

the automake update and is looking into it.

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

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

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

Darren,
I have reworked the commits to fix issues while building on other distros.
Can you check this branch http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=nitin/grub-efi
It is working for me on Fedora 14, for which the other grub-efi commit was failing for me.

Thanks,
Nitin

On 01/16/2012 10:44 AM, Bruce Ashfield wrote:

On 12-01-16 01:40 PM, Bodke, Kishore K wrote:

Hi,

I get build failure for the rt.

ERROR: Function 'do_patch' failed (see
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
for further information)

ERROR: Logfile of failure stored in:
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459

Log data follows:

| ERROR: Function 'do_patch' failed (see
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
for further information)

| Deleted branch meta-temp (was 620917d).

|

| ERROR: patch
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
is not available

This is the problem. But I could have sworn that I fixed this, and
send a merge request. When I just checked now, it still looks broken.

That being said, we should have seen this before now. Are any -rt
kernels being build regularly on master ?

I just checked with Beth and we are not. I will open a bug against the
autobuilder, we need to do this regularly.

--
Darren

It is partially due to meta-kernel-dev picking up new kernel tools that
do strict checking on patches by default (hence my question about
anyone else building this on master).

I'm pushing a fix out now to the meta branch and will send it along
with my next consolidated pull request.

Cheers,

Bruce

|

| ERROR. Could not find an excutable target for
yocto/standard/preempt-rt/base

| ERROR. Could not locate meta series for preempt-rt-standard

| ERROR. Could not modify yocto/standard/preempt-rt/base

NOTE: package
linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
task do_patch: Failed

NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded

ERROR: Task 3
(/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
do_patch) failed with exit code '1'

Is this anything to do with meta-kernel-dev I am using or something else?

Thanks

Kishore.

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

On 12-01-16 01:40 PM, Bodke, Kishore K wrote:

Hi,

I get build failure for the rt.

ERROR: Function 'do_patch' failed (see
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
for further information)

ERROR: Logfile of failure stored in:
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459

Log data follows:

| ERROR: Function 'do_patch' failed (see
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
for further information)

| Deleted branch meta-temp (was 620917d).

|

| ERROR: patch
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
is not available

This is the problem. But I could have sworn that I fixed this, and
send a merge request. When I just checked now, it still looks broken.

That being said, we should have seen this before now. Are any -rt
kernels being build regularly on master ?

It is partially due to meta-kernel-dev picking up new kernel tools that
do strict checking on patches by default (hence my question about
anyone else building this on master).

I'm pushing a fix out now to the meta branch and will send it along
with my next consolidated pull request.

Cheers,

Bruce

|

| ERROR. Could not find an excutable target for
yocto/standard/preempt-rt/base

| ERROR. Could not locate meta series for preempt-rt-standard

| ERROR. Could not modify yocto/standard/preempt-rt/base

NOTE: package
linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
task do_patch: Failed

NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded

ERROR: Task 3
(/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
do_patch) failed with exit code '1'

Is this anything to do with meta-kernel-dev I am using or something else?

Thanks

Kishore.

On 13/01/12 17:27, Jim Abernathy wrote:

under the poky directory you git checkout of the branch you want to work with, then you clone meta-intel and within that directory you checkout a branch. if you needed to use git for you personal project, you can't put it at the same meta-intel level, right? Only one per directory??? I would guess that you'd need to create your personal git clone below meta-intel; something like meta-jima.

Does this sound correct??

Jim A

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

Hi Jim,

This is indeed how I manage my extra package files and anything else poky needs. Any other interesting input would be good to hear though!

Slightly off-topic, with meta-intel and then checking out branches to get specific machines, do you do global work in master, machine specific work in the branches, and then merge out from master to the branches to keep them all in sync?

Cheers,
Jack.

Hi all,
The overall open bug trend increased a little last week. The new submitted bug vs. fixed bug number is 17 vs. 21. WDD number is 675. Bug status of WW02 could be found on https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun

Hey Koen, good to hear from you.  My next step is to bring meta-ti.  I've been following that list so I hope to get things working with it soon.

Regards,

Brian

From Droid Incredible

Op 11 jan. 2012, om 21:57 heeft Brian Hutchinson het volgende geschreven:

On Wed, Jan 11, 2012 at 3:47 PM, Joshua Lock <josh@...> wrote:

In meta-yocto/conf/distro/poky.conf there's a line which sets:

PREFERRED_VERSION_linux-yocto ?= "2.6.37+git%"

Which is then overridden for the qemu machines to:

PREFERRED_VERSION_linux-yocto_qemuppc ?= "3.0%"

If you add a similar line for beagleboard to a conf file, such as
local.conf, it would look for a 3.0 kernel version and use your tree.

PREFERRED_VERSION_linux-yocto_beagleboard ?= "3.0%"

I know you've switched to master but I wanted to help you understand the
system is doing what it is.

Ah, very good! Yes, good to know information. I'm coming from
OE-Angstrom/Arago and so far most things have been pretty familiar but
it always helps to know how it fits together. I need to make several
BSP's for TI processors and this helps me understand things a bit
better.

If that's the case, you'd be a lot better off basing it off the official TI BSP layer instead of meta-yocto.