[yocto] pre-built yocto toolchains don't install cleanly on fedora 19

2013-07-16 Thread Robert P. J. Day 

  the current yocto arm toolchain here:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.0/toolchain/i686/

doesn't install cleanly on fedora 19, a number of people who tried it
got a relocation error. i'll try it again later today and document it
more completely but i'm teaching all week so my testing time is
limited.

  can someone else try it -- just try to install the arm toolchain on
f19 by running script and see what happens. the same relocation error
doesn't happen on ubuntu.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] pre-built yocto toolchains don't install cleanly on fedora 19

2013-07-16 Thread Laurentiu Palcu 
I'm on it. The issue is tracked here:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4853

Thanks,
Laurentiu

On Tue, Jul 16, 2013 at 04:18:24AM -0700, Robert P. J. Day wrote:
> 
>   the current yocto arm toolchain here:
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.0/toolchain/i686/
> 
> doesn't install cleanly on fedora 19, a number of people who tried it
> got a relocation error. i'll try it again later today and document it
> more completely but i'm teaching all week so my testing time is
> limited.
> 
>   can someone else try it -- just try to install the arm toolchain on
> f19 by running script and see what happens. the same relocation error
> doesn't happen on ubuntu.
> 
> rday
> 
> -- 
> 
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
> 
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> ___
> 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] Regarding offline build

2013-07-16 Thread Amit Kumar 
Hi,
I have quarry regarding the Yocto Project build offline.
Is that possible to build the Yocto Project with internet access?
I have download the poky-.tar.bz2, now I wants to build it 
independently without having internet connection.
Do I need to download any other packages also to build it offline?



Thanks & Regards
Amit K


The contents of this e-mail and any attachment(s) may contain confidential or 
privileged information for the intended recipient(s). Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail and 
using or disseminating the information, and must notify the sender and delete 
it from their system. L&T Infotech will not accept responsibility or liability 
for the accuracy or completeness of, or the presence of any virus or disabling 
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] pre-built yocto toolchains don't install cleanly on fedora 19

2013-07-16 Thread Robert P. J. Day 
On Tue, 16 Jul 2013, Robert P. J. Day wrote:

>
>   the current yocto arm toolchain here:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.0/toolchain/i686/
>
> doesn't install cleanly on fedora 19, a number of people who tried it
> got a relocation error. i'll try it again later today and document it
> more completely but i'm teaching all week so my testing time is
> limited.

  whoops, sorry, link to wrong directory, the toolchain in question is
here:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/toolchain/i686/

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] pre-built yocto toolchains don't install cleanly on fedora 19

2013-07-16 Thread Robert P. J. Day 
On Tue, 16 Jul 2013, Laurentiu Palcu wrote:

> I'm on it. The issue is tracked here:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4853

  ok, just added myself to CC list, thanks.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] pre-built yocto toolchains don't install cleanly on fedora 19

2013-07-16 Thread Laurentiu Palcu 
There a fix for this on oe-core ML:
http://patches.openembedded.org/patch/53761/

Thanks,
Laurentiu

On Tue, Jul 16, 2013 at 04:40:38AM -0700, Robert P. J. Day wrote:
> On Tue, 16 Jul 2013, Robert P. J. Day wrote:
> 
> >
> >   the current yocto arm toolchain here:
> >
> > http://downloads.yoctoproject.org/releases/yocto/yocto-1.0/toolchain/i686/
> >
> > doesn't install cleanly on fedora 19, a number of people who tried it
> > got a relocation error. i'll try it again later today and document it
> > more completely but i'm teaching all week so my testing time is
> > limited.
> 
>   whoops, sorry, link to wrong directory, the toolchain in question is
> here:
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/toolchain/i686/
> 
> rday
> 
> -- 
> 
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
> 
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Regarding offline build

2013-07-16 Thread Stewart, David C 
Amit – you will definitely need an internet connection. What you downloaded is 
just the build tools and metadata which tells bitbake where to find the sources 
on the internet.

If you want to build without an internet connection, you might try downloading 
the build appliance. It's a larger download but contains all of the sources.

Dave

From: Amit Kumar mailto:amit.ku...@lntinfotech.com>>
Date: Tuesday, July 16, 2013 4:21 AM
To: "yocto@yoctoproject.org" 
mailto:yocto@yoctoproject.org>>
Subject: [yocto] Regarding offline build

Hi,
I have quarry regarding the Yocto Project build offline.
Is that possible to build the Yocto Project with internet access?
I have download the poky-.tar.bz2, now I wants to build it 
independently without having internet connection.
Do I need to download any other packages also to build it offline?



Thanks & Regards
Amit K


The contents of this e-mail and any attachment(s) may contain confidential or 
privileged information for the intended recipient(s). Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail and 
using or disseminating the information, and must notify the sender and delete 
it from their system. L&T Infotech will not accept responsibility or liability 
for the accuracy or completeness of, or the presence of any virus or disabling 
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Regarding offline build

2013-07-16 Thread Burton, Ross 
On 16 July 2013 12:21, Amit Kumar  wrote:
> I have quarry regarding the Yocto Project build offline.
>
> Is that possible to build the Yocto Project with internet access?
>
> I have download the poky-.tar.bz2, now I wants to build it
> independently without having internet connection.
>
> Do I need to download any other packages also to build it offline?

If you know what you want to build (i.e. core-image-sato), then
telling bitbake to fetch the sources when you do have a connection
should be mostly sufficient:

$ bitbake core-image-sato -c fetchall

This will download all the sources and put them in the downloads
directory that you've configured in local.conf.

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

[yocto] SDK generation

2013-07-16 Thread Matthias Van Gestel 
Hi I'm having some trouble generating a Qt(4) SDK that I can use on a host
system. We generate our own image edna-image-minimal:

PR="2"

# Copied from meta/recipes-core/images/core-image-minibal.bb

DESCRIPTION = "A small image just capable of allowing a device to boot."

IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP}
${CORE_IMAGE_EXTRA_INSTALL}"

IMAGE_LINGUAS = " "

LICENSE = "MIT"

inherit core-image

# remove not needed ipkg informations
ROOTFS_POSTPROCESS_COMMAND += "remove_packaging_data_files ; "

# Copied from meta/recipes-graphics/images/core-image-x11.bb

IMAGE_FEATURES += "splash package-management x11-base xserver-xf86-config"

# IMAGE_INSTALL += "qtbase qtbase-tools qtbase-plugins"
# qtbase-tools qtbase-plugins"

IMAGE_FEATURES += "qt4-pkgs"
IMAGE_INSTALL += "mini-x-session"
TOOLCHAIN_HOST_TASK += "nativesdk-qemu"
--
Now when I try to generate a SDK with the following command:
MACHINE="qemuarm" bitbake edna-image-minimal -c populate_sdk
The SDK script gets generated, I execute it and it extracts itself.

Now I'd like to know where I can find the native tools to cross compile my
application, I have no qmake or cross-gcc.

Another issue is about the eclipse adt plugin, I installed the plugin
configured the sysroot path and the cross compiler path (it uses scripts
from /opt/poky/1.4.1) and then in the Qemu part I picked the kernel
generated in the build/tmp/deploy/images, but then it complains about a
pseudo and asks about qemu-extract-sdk. So to cut the story short I'm stuck
at generating a decent cross sdk.
(I used the official
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#configuring-the-eclipse-ide-juno
 guide).

How do I proceed, or are there other ways I can do to get a decent SDK
working?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Regarding offline build

2013-07-16 Thread Lee_Ballard 
We do offline builds.  You need to download all the tar balls for all the open 
source recipes you build, or you can download pre-build images and SDK.  
Another way is to create a local mirror of all the tar balls you need.

Lee Ballard
Platform Software Principal Engineer
Dell | Enterprise Product Group


From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Amit Kumar
Sent: Tuesday, July 16, 2013 6:22 AM
To: yocto@yoctoproject.org
Subject: [yocto] Regarding offline build

Hi,
I have quarry regarding the Yocto Project build offline.
Is that possible to build the Yocto Project with internet access?
I have download the poky-.tar.bz2, now I wants to build it 
independently without having internet connection.
Do I need to download any other packages also to build it offline?



Thanks & Regards
Amit K


The contents of this e-mail and any attachment(s) may contain confidential or 
privileged information for the intended recipient(s). Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail and 
using or disseminating the information, and must notify the sender and delete 
it from their system. L&T Infotech will not accept responsibility or liability 
for the accuracy or completeness of, or the presence of any virus or disabling 
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] zedboard & gnuradio

2013-07-16 Thread Edward Vidal 
Hello,
Any and all help will be appreciated.
testing not having to revert back to boost-1.53.0 The new pull of poky,
meta-oe, boost-1.54.0 compiled okay.
pull on 07/16/13 of all meta_data_from_remotes
cd POKY/build071613_zedboard/
cp -R ~/POKY/meta_data_from_remotes/poky/ .
cd poky/
cp -R ~/POKY/meta_data_from_remotes/meta-oe/ .
cp -R ~/POKY/meta_data_from_remotes/meta-xilinx/ .
p -R ~/POKY/meta_data_from_remotes/meta-java .
. oe-init-build-env
cp ~/POKY/build071613_zedboard/local.conf conf/
cp ~/POKY/build071613_zedboard/bblayers.conf conf/
cp ../../core-image-minimal-ex.bb ../meta/recipes-core/images/
/home/vidal/POKY/poky/patch_sato_gnuplot
MACHINE=zedboard bitbake core-image-minimal-ex 4333 tasks
Build Configuration:
BB_VERSION= "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard"
DISTRO    = "poky"
DISTRO_VERSION= "1.4+snapshot-20130716"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "master:3dee534f1e25109e0bdb681de0746c336f4b8840"
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = "master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff"
meta-oe   = "master:c383d6230942bb1558cee02764bced09031cb70f"
meta-java = "master:59696d89fd33df6953dcb2dd54ccd3b362513f28"
meta-yocto-bsp= "master:3dee534f1e25109e0bdb681de0746c336f4b8840"
WARNING: QA Issue: Found library in wrong location:
/usr/bin/qt4/examples/tools/plugandpaint/plugins/libpnp_extrafilters.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/plugandpaint/plugins/.debug/libpnp_extrafilters.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/styleplugin/styles/libsimplestyleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/styleplugin/styles/.debug/libsimplestyleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/echoplugin/plugin/libechoplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/echoplugin/plugin/.debug/libechoplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/.debug/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/.debug/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/libqmlqtimeexampleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/.debug/libqmlqtimeexampleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/libqmlimageproviderplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/.debug/libqmlimageproviderplugin.so


ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
from qwt was already stripped, this will prevent future debugging!
ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
stripped, this will prevent future debugging!
ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already
stripped, this will prevent future debugging!
WARNING: QA Issue: Found library in wrong location:
/usr/plugins/designer/libqwt_designer_plugin.so
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/home/vidal/POKY/build071613_zedboard/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qwt/6.0.1-r1/temp/log.do_package.27159
ERROR: Task 1126
(/home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/
qwt_6.0.1.bb, do_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4315 tasks of which 368 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/
qwt_6.0.1.bb, do_package
Summary: There were 5 WARNING messages shown.
Summary: There were 5 ERROR messages shown, returning a non-zero exit code.
I will be looking where the qt libs need to be installed.

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

[yocto] 回复： [meta-freescale] how to install pulseaudio completely

2013-07-16 Thread jojo 
Hi,  
Ok & i will have a try, thanks for your reply :)

Thanks,

- Jojo


在 2013年7月12日星期五，下午6:45，Erik Botö 写道：

> Hi,  
> On Fri, Jul 12, 2013 at 12:35 PM, jojo  (mailto:rjie...@gmail.com)> wrote:
> > Hi,  
> > My yocto version/tag is dylan.
> >  
> > I have compiled fsl-image-gui to testing the the audio output, but i can 
> > not find
> > anything about for pulseaudio server to start up daemon.
> >  
> > I saw the build code in the path about for 
> > "build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/pulseaudio/3.0-r0/image/"
> >   
> > and it really have built all things of pulseaudio. but when i create the 
> > fsl-image-gui to start up, i just find "libpulse*" in the
> > rootfs.
> >  
> > I think that something wrong with pulseaudio configure so that it do not 
> > install completely by default.
>  
> The pulseaudio daemon is packaged as pulseaudio-server, maybe the image 
> doesn't install that package by default?  
>   
> Cheers,  
> Erik Botö
>  
> >  
> > someone know about that how to install pulseaudio completely ?  
> >  
> > Thanks,
> >  
> > - Jojo
> >  
> >  
> > ___
> > meta-freescale mailing list
> > meta-freesc...@yoctoproject.org (mailto:meta-freesc...@yoctoproject.org)
> > https://lists.yoctoproject.org/listinfo/meta-freescale
> >  
>  

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

Re: [yocto] [yocto-autobuilder][PATCH 0/3] Enabling of the new testimage class for sanity tests

2013-07-16 Thread Flanagan, Elizabeth 
Merged into master and production. Thanks.

-b

On Wed, Jul 10, 2013 at 10:32 AM, Stefan Stanacar
 wrote:
> Hi Beth,
>
> The first two patches enable the new testimage class that has just been 
> merged in master,
> and it needs a real AB shakedown ;).
>
> On my local AB one of the problems I've had were timeouts
> for qemu booting (when the machine was really loaded), and I've sent a patch 
> to increase the timeout, but
> this might need a little more tweaking for the Yocto AB. Also, one more setup 
> issue could be DISPLAY / vnc server.
> I've had some trouble with DISPLAY=localhost:1 that's why you'll notice
> I've used DISPLAY=:1, that fixed the problem out on my machine. It has 
> something to do with how the new class starts the runqemu script
> and the enviroment.
>
>
> The last patch has nothing to do with enabling, I just thought that we should 
> run the sanity tests
> for the sdk images too given that the new class has a gcc test. It adds a few 
> minutes to the builds,
> keep this one out if that's problem.
>
> Cheers,
> Stefan
>
> The following changes since commit b26b257e16fddb7730d3b2a0c55c4b43a48ae54c:
>
>   Revert "buildset-config: build core-image-sato SDK" (2013-07-02 17:10:05 
> -0700)
>
> are available in the git repository at:
>
>   git://mirror.rb.intel.com/git.yoctoproject.org/poky-contrib 
> stefans/yab-newsanity3
>
> for you to fetch changes up to e15d6185251e4c6f163577c7263239936d76e5b3:
>
>   buildsets: run sanity tests for core-image-sato-sdk images (2013-07-10 
> 19:07:27 +0300)
>
> 
> Stefan Stanacar (3):
>   RunSanityTests: add support for the new testimage class
>   nightly-multilib,qa-systemd.conf: enable specific tests with the new 
> class
>   buildsets: run sanity tests for core-image-sato-sdk images
>
>  buildset-config/nightly-arm.conf   |  2 +-
>  buildset-config/nightly-mips.conf  |  2 +-
>  buildset-config/nightly-multilib.conf  |  8 +++
>  buildset-config/nightly-ppc.conf   |  2 +-
>  buildset-config/nightly-qa-systemd.conf|  4 ++--
>  buildset-config/nightly-x86-64.conf|  2 +-
>  buildset-config/nightly-x86.conf   |  2 +-
>  .../autobuilder/buildsteps/RunSanityTests.py   | 27 
> --
>  8 files changed, 31 insertions(+), 18 deletions(-)
>
> Stefan Stanacar (3):
>   RunSanityTests: add support for the new testimage class
>   nightly-multilib,qa-systemd.conf: enable specific tests with the new
> class
>   buildsets: run sanity tests for core-image-sato-sdk images
>
>  buildset-config/nightly-arm.conf   |  2 +-
>  buildset-config/nightly-mips.conf  |  2 +-
>  buildset-config/nightly-multilib.conf  |  8 +++
>  buildset-config/nightly-ppc.conf   |  2 +-
>  buildset-config/nightly-qa-systemd.conf|  4 ++--
>  buildset-config/nightly-x86-64.conf|  2 +-
>  buildset-config/nightly-x86.conf   |  2 +-
>  .../autobuilder/buildsteps/RunSanityTests.py   | 27 
> --
>  8 files changed, 31 insertions(+), 18 deletions(-)
>
> --
> 1.8.1.4
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Image recipes in Yocto 1.4 (dylan-9.0.0)

2013-07-16 Thread Paul Eggleton 
Hi Brian,

Sorry this message got lost in my inbox.

On Monday 24 June 2013 16:22:27 Brian Karcz wrote:
> > Paul Eggleton wrote:
> > > Brian Karcz wrote:
> > > Is there a way to stop this optimization and have the image build 
> > > populate the work directory as it has in the past?
> > 
> > You should be able to do this in your image recipe:
> > 
> > python () {
> > d.delVarFlag("do_fetch", "noexec")
> > d.delVarFlag("do_unpack", "noexec") 
> > }
>
> That was what I needed to get my build(s) moving forward. It has brought me
> to a follow-up question. The image in question (a ramdisk image) is being
> built as a dependency of a larger image build. When I rebuild the parent
> image, bitbake believes the child image needs to be rebuilt, but when this
> occurs, do_fetch and do_unpack once again don't get executed and my build
> fails as before when it jumps straight to do_rootfs with an empty work
> directory. Upon seeing this, I attempted to re-build the child image from
> its own recipe, without trying to build the parent, and the same behavior
> occurs.
> 
> I was considering adding the child image to RM_WORK_EXCLUDE in local.conf,
> but that didn't seem intuitive to the problem. 

So you are using rm_work? If you are I don't think RM_WORK_EXCLUDE will really 
help.

Just to confirm, you're not referring to the WORKDIR of one recipe within the 
other are you? Also, how are you setting up the dependency relationship 
between the images?

> I would think bitbake would do nothing since nothing has changed, or the
> required tasks would be executed, but I wouldn't think telling the last
> build to leave the work area would be the fix.
> 
> Do have any thoughts on making this work past a single build?

So I haven't tested this exact configuration; it's possible that bitbake is 
eliminating a dependency based on the task being marked as "noexec", but I 
wouldn't have thought so.

Cheers,
Paul

PS: please keep replies on the mailing list. Thanks.

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] zedboard & gnuradio

2013-07-16 Thread Paul Eggleton 
Hi Edward,

On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote:
> ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
> from qwt was already stripped, this will prevent future debugging!
> ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
> stripped, this will prevent future debugging!
> ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already
> stripped, this will prevent future debugging!

poky.conf now marks this QA issue as an error instead of a warning in order to 
pick up on quality issues when running builds. You can either:

a) Fix the recipe so that qwt gets built without stripping its output 
binaries, or

b) set your own value for ERROR_QA and WARN_QA so that "already-stripped" 
appears in WARN_QA rather than ERROR_QA

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-autobuilder][PATCH 0/3] Enabling of the new testimage class for sanity tests

2013-07-16 Thread Saul Wold 

On 07/16/2013 09:12 AM, Flanagan, Elizabeth wrote:

Merged into master and production. Thanks.



Turns out the buildtools-tarball does not have all the python modules 
needed, I am working this issue right now.


Sau!


-b

On Wed, Jul 10, 2013 at 10:32 AM, Stefan Stanacar
 wrote:

Hi Beth,

The first two patches enable the new testimage class that has just been merged 
in master,
and it needs a real AB shakedown ;).

On my local AB one of the problems I've had were timeouts
for qemu booting (when the machine was really loaded), and I've sent a patch to 
increase the timeout, but
this might need a little more tweaking for the Yocto AB. Also, one more setup 
issue could be DISPLAY / vnc server.
I've had some trouble with DISPLAY=localhost:1 that's why you'll notice
I've used DISPLAY=:1, that fixed the problem out on my machine. It has 
something to do with how the new class starts the runqemu script
and the enviroment.


The last patch has nothing to do with enabling, I just thought that we should 
run the sanity tests
for the sdk images too given that the new class has a gcc test. It adds a few 
minutes to the builds,
keep this one out if that's problem.

Cheers,
Stefan

The following changes since commit b26b257e16fddb7730d3b2a0c55c4b43a48ae54c:

   Revert "buildset-config: build core-image-sato SDK" (2013-07-02 17:10:05 
-0700)

are available in the git repository at:

   git://mirror.rb.intel.com/git.yoctoproject.org/poky-contrib 
stefans/yab-newsanity3

for you to fetch changes up to e15d6185251e4c6f163577c7263239936d76e5b3:

   buildsets: run sanity tests for core-image-sato-sdk images (2013-07-10 
19:07:27 +0300)


Stefan Stanacar (3):
   RunSanityTests: add support for the new testimage class
   nightly-multilib,qa-systemd.conf: enable specific tests with the new 
class
   buildsets: run sanity tests for core-image-sato-sdk images

  buildset-config/nightly-arm.conf   |  2 +-
  buildset-config/nightly-mips.conf  |  2 +-
  buildset-config/nightly-multilib.conf  |  8 +++
  buildset-config/nightly-ppc.conf   |  2 +-
  buildset-config/nightly-qa-systemd.conf|  4 ++--
  buildset-config/nightly-x86-64.conf|  2 +-
  buildset-config/nightly-x86.conf   |  2 +-
  .../autobuilder/buildsteps/RunSanityTests.py   | 27 --
  8 files changed, 31 insertions(+), 18 deletions(-)

Stefan Stanacar (3):
   RunSanityTests: add support for the new testimage class
   nightly-multilib,qa-systemd.conf: enable specific tests with the new
 class
   buildsets: run sanity tests for core-image-sato-sdk images

  buildset-config/nightly-arm.conf   |  2 +-
  buildset-config/nightly-mips.conf  |  2 +-
  buildset-config/nightly-multilib.conf  |  8 +++
  buildset-config/nightly-ppc.conf   |  2 +-
  buildset-config/nightly-qa-systemd.conf|  4 ++--
  buildset-config/nightly-x86-64.conf|  2 +-
  buildset-config/nightly-x86.conf   |  2 +-
  .../autobuilder/buildsteps/RunSanityTests.py   | 27 --
  8 files changed, 31 insertions(+), 18 deletions(-)

--
1.8.1.4






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

Re: [yocto] zedboard & gnuradio

2013-07-16 Thread Edward Vidal 
Paul,
I opted for options b.)  modifying
/home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf
mvoing already-stripped from  ERROR_QA to WARN_QA .
Build is currently in progress.
My question will option a.)  need to be done to prevent this from occurring
in future releases.
Thanks not working with the variables would have made this extremely
difficult to find and fix.


On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> Hi Edward,
>
> On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote:
> > ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
> > from qwt was already stripped, this will prevent future debugging!
> > ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
> > stripped, this will prevent future debugging!
> > ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was
> already
> > stripped, this will prevent future debugging!
>
> poky.conf now marks this QA issue as an error instead of a warning in
> order to
> pick up on quality issues when running builds. You can either:
>
> a) Fix the recipe so that qwt gets built without stripping its output
> binaries, or
>
> b) set your own value for ERROR_QA and WARN_QA so that "already-stripped"
> appears in WARN_QA rather than ERROR_QA
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto + meta-networking

2013-07-16 Thread Brian Hutchinson 
Hi,

What is the "right" way of adding the meta-networking to Yocto?  I'm
obviously not doing something right.

At the poky directory level, I cloned meta-openembedded.  I then tried to
go to my build's local.conf and adding meta-networking and meta-oe layers
and I'm getting a dependency message when I try to bitbake net-snmp that
says:

ERROR: Layer dependency core of layer networking not found

This makes me think that meta-openembedded is wanting openembedded-core but
I've never tried to use that with Yocto before so I thought I better ask
before I totally mess up my build environment.

I have a rootfilesystem build based on Denzil and I need net-snmp and the
meta-networking Denzil branch is pretty much empty so I cloned master in
order to get net-snmp so I don't know if mixing branches could be my
problem (don't know how much that matters but I usually try to use the same
release branch of various components).

I've looked for examples of this kind of setup but haven't found much.

Regards,

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

Re: [yocto] Yocto + meta-networking

2013-07-16 Thread Saul Wold 

On 07/16/2013 02:06 PM, Brian Hutchinson wrote:

Hi,

What is the "right" way of adding the meta-networking to Yocto?  I'm
obviously not doing something right.

At the poky directory level, I cloned meta-openembedded.  I then tried
to go to my build's local.conf and adding meta-networking and meta-oe
layers and I'm getting a dependency message when I try to bitbake
net-snmp that says:

Did you mean your bblayers.conf file?  I am not sure you need meta-oe if 
you are just building net-snmp, this is what your bblayers.conf should 
look like:


BBLAYERS ?= " \
  /home/sgw/yocto/poky/meta \
  /home/sgw/yocto/poky/meta-yocto \
  /home/sgw/yocto/poky/meta-yocto-bsp \
  /home/sgw/yocto/layers/meta-openembedded/meta-networking \
  "

This is from a POKY build, if this is oe-core alone then you would not 
have the meta-yocto* layers.


Sau!



ERROR: Layer dependency core of layer networking not found

This makes me think that meta-openembedded is wanting openembedded-core
but I've never tried to use that with Yocto before so I thought I better
ask before I totally mess up my build environment.

I have a rootfilesystem build based on Denzil and I need net-snmp and
the meta-networking Denzil branch is pretty much empty so I cloned
master in order to get net-snmp so I don't know if mixing branches could
be my problem (don't know how much that matters but I usually try to use
the same release branch of various components).

I've looked for examples of this kind of setup but haven't found much.

Regards,

Brian



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


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

Re: [yocto] Yocto + meta-networking

2013-07-16 Thread Paul Eggleton 
Hi Brian,

On Tuesday 16 July 2013 17:06:46 Brian Hutchinson wrote:
> What is the "right" way of adding the meta-networking to Yocto?  I'm
> obviously not doing something right.
> 
> At the poky directory level, I cloned meta-openembedded.  I then tried to
> go to my build's local.conf and adding meta-networking and meta-oe layers
> and I'm getting a dependency message when I try to bitbake net-snmp that
> says:
> 
> ERROR: Layer dependency core of layer networking not found
> 
> This makes me think that meta-openembedded is wanting openembedded-core but
> I've never tried to use that with Yocto before so I thought I better ask
> before I totally mess up my build environment.
> 
> I have a rootfilesystem build based on Denzil and I need net-snmp and the
> meta-networking Denzil branch is pretty much empty so I cloned master in
> order to get net-snmp so I don't know if mixing branches could be my
> problem (don't know how much that matters but I usually try to use the same
> release branch of various components).

Mixing branches is the issue here. meta-networking added a LAYERDEPENDS on 
"core" which the denzil poky/OE-Core doesn't provide. This is just an 
incidental error though, if it hadn't failed on this you'd have hit other 
problems.

meta-networking wasn't even around in the denzil days. If you need net-snmp 
from there on top of denzil the only way is to backport the recipe and any 
missing dependencies and add it to an additional layer (assuming you don't 
already have a layer for customisations). In practice backporting should be 
fairly trivial; I'd suggest copying the recipe over and seeing how far you 
get.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto + meta-networking

2013-07-16 Thread Brian Hutchinson 
Hi Saul,

Sorry for top posting, I'm responding on my phone.

Yes, that's exactly how my bblayers.conf looks except when I had the first
problem I then added in meta-oe.  I'll double check and make sure I didn't
do something stupid like use a spoiled shell env etc.

Note, I didn't check out meta-openembedded to layers dir, I did it in the
same dir as poky ... maybe that is my problem.

Regards,

Brian
On Jul 16, 2013 5:19 PM, "Saul Wold"  wrote:

> On 07/16/2013 02:06 PM, Brian Hutchinson wrote:
>
>> Hi,
>>
>> What is the "right" way of adding the meta-networking to Yocto?  I'm
>> obviously not doing something right.
>>
>> At the poky directory level, I cloned meta-openembedded.  I then tried
>> to go to my build's local.conf and adding meta-networking and meta-oe
>> layers and I'm getting a dependency message when I try to bitbake
>> net-snmp that says:
>>
>>  Did you mean your bblayers.conf file?  I am not sure you need meta-oe if
> you are just building net-snmp, this is what your bblayers.conf should look
> like:
>
> BBLAYERS ?= " \
>   /home/sgw/yocto/poky/meta \
>   /home/sgw/yocto/poky/meta-**yocto \
>   /home/sgw/yocto/poky/meta-**yocto-bsp \
>   /home/sgw/yocto/layers/meta-**openembedded/meta-networking \
>   "
>
> This is from a POKY build, if this is oe-core alone then you would not
> have the meta-yocto* layers.
>
> Sau!
>
>
>  ERROR: Layer dependency core of layer networking not found
>>
>> This makes me think that meta-openembedded is wanting openembedded-core
>> but I've never tried to use that with Yocto before so I thought I better
>> ask before I totally mess up my build environment.
>>
>> I have a rootfilesystem build based on Denzil and I need net-snmp and
>> the meta-networking Denzil branch is pretty much empty so I cloned
>> master in order to get net-snmp so I don't know if mixing branches could
>> be my problem (don't know how much that matters but I usually try to use
>> the same release branch of various components).
>>
>> I've looked for examples of this kind of setup but haven't found much.
>>
>> Regards,
>>
>> Brian
>>
>>
>>
>> __**_
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.**org/listinfo/yocto
>>
>>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto Digest, Vol 34, Issue 38

2013-07-16 Thread Zafrullah Syed 
Hi,

I added opencv
in /home/yocto/poky/meta-gumstix-extras/recipes-images/gumstix/
gumstix-console-image.bb.

Why do I need to add  'IMAGE_EXTRAS += "opencv-apps opencv-samples" in
local.conf? aren't we supposed to add it in
/home/yocto/poky/meta-gumstix-extras/recipes-images/gumstix/
gumstix-console-image.bb? I am confused here.

I added Gstreamer along with opencv in (gumstix-console-image.bb) and build
was successful. Gstreamer was added to Image but not opencv.

Is it not sufficient if we add just 'opencv' in
/home/yocto/poky/meta-gumstix-extras/recipes-images/gumstix/
gumstix-console-image.bb? what are these 'opencv-apps opencv-samples' files?

Regards,
Zafrullah Syed


On Fri, Jul 12, 2013 at 9:00 PM,  wrote:

> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
>1. Libraries missing after build is successful (Zafrullah Syed)
>2. Re: Libraries missing after build is successful (Gary Thomas)
>3. Re: Fwd: Yocto Layers not getting recognized by bitbake
>   (varun bhatnagar)
>4. meta-security Layer Now Available (Jeff Osier-Mixon)
>
>
> --
>
> Message: 1
> Date: Fri, 12 Jul 2013 17:21:39 +0200
> From: Zafrullah Syed 
> To: yocto 
> Subject: [yocto] Libraries missing after build is successful
> Message-ID:
>  iv...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I appended OpenCV and Gstreamer plugins to Image and made a build. Build is
> successful without any errors but OpenCV libraries are missing in
> rootfs.tar.bz2
>
> I searched for libs( libopencv_core.so, libhighgui.so, libOpenCV.so ) in
> /usr/bin, /usr/lib and the whole archive but unable to find any libraries.
>
> In /yocto/build/downloads, I can
> see OpenCV-2.4.3.tar.bz2, OpenCV-2.4.3.tar.bz2.done files.
>
> In /yocto/build/tmp/deploy/licenses, I can see OpenCV folder.
>
> In /yocto/build/tmp/deploy/rpm/armv7a_vfp_neon, I can see .rpm packages.
>
> Log file after build says this:
> (Pasted only start and success logs)
>
> NOTE: recipe opencv-2.4.3-r2: task do_compile: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_install: Started
> NOTE: recipe opencv-2.4.3-r2: task do_install: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_package: Started
> NOTE: recipe opencv-2.4.3-r2: task do_populate_sysroot: Started
> NOTE: recipe opencv-2.4.3-r2: task do_populate_sysroot: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_package: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_package_write_rpm: Started
> NOTE: recipe opencv-2.4.3-r2: task do_package_write_rpm: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_generate_toolchain_file: Started
> NOTE: recipe opencv-2.4.3-r2: task do_generate_toolchain_file: Succeeded
> NOTE: recipe opencv-2.4.3-r2: task do_populate_lic: Started
> NOTE: recipe opencv-2.4.3-r2: task do_populate_lic: Succeeded
>
> Any Idea/hints where these files are and why they are missing?
>
> Regards,
> Zafrullah Syed.
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://lists.yoctoproject.org/pipermail/yocto/attachments/20130712/482fc477/attachment-0001.html
> >
>
> --
>
> Message: 2
> Date: Fri, 12 Jul 2013 10:21:54 -0600
> From: Gary Thomas 
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Libraries missing after build is successful
> Message-ID: <51e02d22.1090...@mlbassoc.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 2013-07-12 09:21, Zafrullah Syed wrote:
> > I appended OpenCV and Gstreamer plugins to Image and made a build. Build
> is successful without any errors but OpenCV libraries are missing in
> rootfs.tar.bz2
>
> How did you do this?
>
> You should be able to just add them in your local.conf, e.g.
>IMAGE_EXTRAS += "opencv-apps opencv-samples"
> etc.
>
> > I searched for libs( libopencv_core.so, libhighgui.so, libOpenCV.so ) in
> /usr/bin, /usr/lib and the whole archive but unable to find any libraries.
> >
> > In /yocto/build/downloads, I can see OpenCV-2.4.3.tar.bz2,
> OpenCV-2.4.3.tar.bz2.done files.
> >
> > In /yocto/build/tmp/deploy/licenses, I can see OpenCV folder.
> >
> > In /yocto/build/tmp/deploy/rpm/armv7a_vfp_neon, I can see .rpm packages.
> >
> > Log file after build says this:
> > (Pasted only start and success logs)
> >
> > NOTE: recipe opencv-2.4.3-r2: task do_compile: Succeeded
> > NOTE: recipe opencv-2.4.3-r2: task do_install: Started
> > NOTE: recipe opencv-2.4.3-r2: task do_install: Succeeded
> > NOTE: recipe openc

Re: [yocto] zedboard & gnuradio

2013-07-16 Thread Edward Vidal 
Hello,
with the change that Paul recommended the  errors turned into 4 warnings
ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
from qwt was already stripped, this will prevent future debugging!
ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
stripped, this will prevent future debugging!
ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already
stripped, this will prevent future debugging!
WARNING: QA Issue: Found library in wrong location:
/usr/plugins/designer/libqwt_designer_plugin.so
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/home/vidal/POKY/build071613_zedboard/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qwt/6.0.1-r1/temp/log.do_package.27159
ERROR: Task 1126
(/home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/
qwt_6.0.1.bb, do_package) failed with exit code '1'

WARNING: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
from qwt was already stripped, this will prevent future debugging!
WARNING: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
stripped, this will prevent future debugging!
WARNING: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was
already stripped, this will prevent future debugging!
WARNING: QA Issue: Found library in wrong location:
/usr/plugins/designer/libqwt_designer_plugin.so
NOTE: Tasks Summary: Attempted 4333 tasks of which 3960 didn't need to be
rerun and all succeeded
Thanks for all the help..


On Tue, Jul 16, 2013 at 1:18 PM, Edward Vidal wrote:

> Paul,
> I opted for options b.)  modifying
> /home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf
> mvoing already-stripped from  ERROR_QA to WARN_QA .
> Build is currently in progress.
> My question will option a.)  need to be done to prevent this from
> occurring in future releases.
> Thanks not working with the variables would have made this extremely
> difficult to find and fix.
>
>
> On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton <
> paul.eggle...@linux.intel.com> wrote:
>
>> Hi Edward,
>>
>> On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote:
>> > ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
>> > from qwt was already stripped, this will prevent future debugging!
>> > ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
>> > stripped, this will prevent future debugging!
>> > ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was
>> already
>> > stripped, this will prevent future debugging!
>>
>> poky.conf now marks this QA issue as an error instead of a warning in
>> order to
>> pick up on quality issues when running builds. You can either:
>>
>> a) Fix the recipe so that qwt gets built without stripping its output
>> binaries, or
>>
>> b) set your own value for ERROR_QA and WARN_QA so that "already-stripped"
>> appears in WARN_QA rather than ERROR_QA
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>>
>
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] zedboard & gnuradio

2013-07-16 Thread Paul Eggleton 
On Tuesday 16 July 2013 13:18:07 Edward Vidal wrote:
> On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton
>  wrote:
> > On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote:
> > > ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so'
> > > from qwt was already stripped, this will prevent future debugging!
> > > ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already
> > > stripped, this will prevent future debugging!
> > > ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was
> > > already stripped, this will prevent future debugging!
> > 
> > poky.conf now marks this QA issue as an error instead of a warning in
> > order to pick up on quality issues when running builds. You can either:
> > 
> > a) Fix the recipe so that qwt gets built without stripping its output
> > binaries, or
> > 
> > b) set your own value for ERROR_QA and WARN_QA so that "already-stripped"
> > appears in WARN_QA rather than ERROR_QA
>
> I opted for options b.)  modifying
> /home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf
> mvoing already-stripped from  ERROR_QA to WARN_QA .
> Build is currently in progress.
> My question will option a.)  need to be done to prevent this from occurring
> in future releases.

The recipe in question is part of meta-oe and thus is maintained by 
OpenEmbedded rather than the Yocto Project, so ultimately someone in the 
OpenEmbedded community should fix it, yes. Fixing "already stripped" issues 
usually isn't too hard, it just depends on how the software in question is 
being built.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Weekly build availability

2013-07-16 Thread Flanagan, Elizabeth 
Sorry for the lateness of the build. The artifacts should be available soon at:

http://autobuilder.yoctoproject.org/pub/nightly/20130717-2

meta-fsl-arme2f010bec19aef73b4731cb4f66c7412d59b265c
meta-fsl-ppc93c57323edc118eb8905980348ad3888664f2382
meta-intel  32a8205cebd5dbd65847c63721dc5df70c4d1c35
meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3
meta-qt3b73552fb998fd30a01dbee5a172e432a16078222
poky3dee534f1e25109e0bdb681de0746c336f4b8840

Please begin weekly testing as soon as artifacts become available.

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto