Re: [yocto] Recent autobuilder changes
On 30 June 2013 23:40, Flanagan, Elizabeth wrote: > This weekend I brought down the autobuilder to implement the new build > failure email formatter. This *should* provide a bit more detailed > information in a much easier to read format. Please, let me know of > any tweaks people might like to see in the message format. Much improved! The one thing I'd love to see though is the relevant branch_* values right at the top, so it's trivial to spot a master vs MUT vs 1.4.1 build. Cheers, Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK
On Fri, 2013-06-28 at 14:24 -0700, Khem Raj wrote: > as an aside, if meta-toolchain is deprecated why should we carry > meta-toolchain-gmae as well? it seems a special SDK > only target. I think it will be better to have sdks from images all > the time. Because the QA testing for Danny and likely Dylan will continue to use meta-toolchain-gmae because that's what their test plan is. Hopefully we can change the autobuilder so that it only builds meta-toolchain-gmae for those releases and not master. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK
On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote: > On 2013-06-27 04:06, Ross Burton wrote: > > The meta-toolchain* recipes are deprecated, so when building > > meta-toolchain-gmae > > also build the SDK for core-image-sato. > > > > Signed-off-by: Ross Burton > > If/when the meta-toolchain recipes go away, how do I create a stand-alone > toolchain > derived from Poky/Yocto (which I use all the time!)? The idiom is to pick an image to base the SDK on, and use the "populate_sdk" task: $ bitbake core-image-sato -c populate_sdk If you want just the compiler and no userspace, then I'm not sure what the best solution going forwards is. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK
What's the reason to deprecate meta-toolchain that is for standalone cross-compiler generation? Is there a replacement? Cheers, Bruce On Mon, Jul 1, 2013 at 5:16 PM, Ross Burton wrote: > On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote: > > On 2013-06-27 04:06, Ross Burton wrote: > > > The meta-toolchain* recipes are deprecated, so when building > meta-toolchain-gmae > > > also build the SDK for core-image-sato. > > > > > > Signed-off-by: Ross Burton > > > > If/when the meta-toolchain recipes go away, how do I create a > stand-alone toolchain > > derived from Poky/Yocto (which I use all the time!)? > > The idiom is to pick an image to base the SDK on, and use the > "populate_sdk" task: > > $ bitbake core-image-sato -c populate_sdk > > If you want just the compiler and no userspace, then I'm not sure what > the best solution going forwards is. > > Ross > > ___ > 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] [PATCH] buildset-config: build core-image-sato SDK
On 1 July 2013 10:24, Kumita Bruce wrote: > What's the reason to deprecate meta-toolchain that is for standalone > cross-compiler generation? Is there a replacement? For full SDKs, generation from images is trivial now and means you don't need to replicate everything. I've no idea about the production of standalone cross-compilers. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: Yocto Layers not getting recognized by bitbake
On Sunday 30 June 2013 00:05:58 varun bhatnagar wrote: > Yes Paul that was the entry was there in CORE_IMAGE_EXTRA_INSTALL. I have > removed it from there but I need to add the command provided by these > packages in my image. So I have added one line in my layer.conf file > "IMAGE_INSTALL_append= test-ea ". Now if I try to run bitbake -k > core-image-minimal, it gives me a message saying "Nothing provides > test-ea". What shall I do? (I have build the recipe file of test-ea without > any error.) Can you show me what the test-ea recipe contains? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fedora 18 CentOS 6.4 yocto difference
Hello, I build images for beagleboard, pandaboard, and beaglebone. The base core-image-sato-sdk with the additonal boost qt-mobility-x11 gsl gnuplot gnuradio openjdk-7-jdk openjdk-7-jre openjdk-7-vm-jamvm openjdk-7-vm-cacao python-netserver Build Configuration: BB_VERSION= "1.18.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-18" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "pandaboard" DISTRO= "poky" DISTRO_VERSION= "1.4.1" TUNE_FEATURES = "armv7a vfp neon" TARGET_FPU= "vfp-neon" meta meta-yocto= "dylan:73f103bf9b2cdf985464dc53bf4f1cfd71d4531f" meta-ti = "(nobranch):d61bfa88ed3df9190ac9fd5643c27f77b34c5f01" meta-oe = "master:ed84e64d22400595b68da4e75b48ab7ecc342aa9" meta-java = "master:59696d89fd33df6953dcb2dd54ccd3b362513f28" meta-yocto-bsp= "dylan:73f103bf9b2cdf985464dc53bf4f1cfd71d4531f" These build okay on a Fedora18 x86_64. On CentOS-6.4-x86_64 I have a problem building the same images. The problem is with numpy which is required by gnuradio. This is the error that I get. | /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64 -L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib -Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so | ERROR: Function failed: do_compile (see /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041 for further information) ERROR: Task 1470 (/home/vidal/POKY/build062913_dylan/poky/meta-oe/meta-oe/recipes-devtools/python/ python-numpy_1.7.0.bb, do_compile) failed with exit code '1' If I remove gnuradio I get a rootfs. NOTE: Tasks Summary: Attempted 7827 tasks of which 681 didn't need to be rerun and all succeeded. Summary: There were 11 WARNING messages shown. After I transfer to a mmc these boot okay. I am thinking that it is python or gcc that is the problem. I have found some sites that show how to upgrade Centos 6.4 to a new python and gcc. These install in non-standard locations. Does anyone know how to tell bitbake where these non-standard locations are located? The version of python on the CentOS-6.4-x86_64 is python-2.6.6-36.el6.x86_64. How to install Python 2.7 and 3.3 on CentOS 6 is at the site below. 1,1 Top http://toomuchdata.com/2012/06/25/how-to-install-python-2-7-3-on-centos-6-2/ After running the commands above your newly installed Python interpreter will be available as /usr/local/bin/python2.7 or /usr/local/bin/python3.3. The system version of Python 2.6.6 will continue to be available as /usr/bin/python and /usr/bin/python2.6. This now has both python 2.6 and python 2.7. Is this the direction that I should be trying? Installing gcc-4.7 cd /etc/yum.reps.d wget http://people.centos.org/tru/devtools-1.1/devtools-1.1.repo [testing-1.1-devtools-$releasever] name=testing 1.1 devtools for CentOS $releasever baseurl=http://people.centos.org/tru/devtools-1.1/$releasever/$basearch/RPMS gpgcheck=0 yum --enablerepo=testing-1.1-devtools-6 install devtoolset-1.1-gcc devtoolset-1.1-gcc-c++ devtoolset-1.1-gcc-gfortran Installed: devtoolset-1.1-gcc.x86_64 0:4.7.2-5.el6 devtoolset-1.1-gcc-c++.x86_64 0:4.7.2-5.el6 devtoolset-1.1-gcc-gfortran.x86_64 0:4.7.2-5.el6 Dependency Installed: devtoolset-1.1-libquadmath-devel.x86_64 0:4.7.2-5.el6 devtoolset-1.1-libstdc++-devel.x86_64 0:4.7.2-5.el6 devtoolset-1.1-runtime.noarch 0:1-13.el6 Complete! export CPP=/opt/centos/devtoolset-1.1/root/usr/bin/cpp export CXX=/opt/centos/devtoolset-1.1/root/usr/bin/c++ export CC=/opt/centos/devtoolset-1.1/root/usr/bin/gcc This is the default gfortran gfortran -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) This is the non-standard gfortran /opt/centos/devtoolset-1.1/root/usr/bin/gfortran -v Using built-in specs. COLLECT_GCC=/opt/centos/devtoolset-1.1/root/usr/bin/gfortran COLLECT_LTO_WRAPPER=/opt/centos/devtoolse
Re: [yocto] Fedora 18 CentOS 6.4 yocto difference
On 1 July 2013 13:37, Edward Vidal wrote: > This is the error that I get. > | /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed > build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o > build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64 > -L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib > -Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o > build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so > | ERROR: Function failed: do_compile (see > /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041 > for further information) > ERROR: Task 1470 > (/home/vidal/POKY/build062913_dylan/poky/meta-oe/meta-oe/recipes-devtools/python/python-numpy_1.7.0.bb, > do_compile) failed with exit code '1' That's not the error, all we have there is a build command and bitbake concluding that there was an error. Because we do parallel make builds, you'll have to scroll back through the compile log to get the actual error. Just sending the entire log to a pastebin will be useful. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: Fedora 18 CentOS 6.4 yocto difference
-- Forwarded message -- From: Edward Vidal Date: Mon, Jul 1, 2013 at 7:16 AM Subject: Re: [yocto] Fedora 18 CentOS 6.4 yocto difference To: "Burton, Ross" /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64 -L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib -Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so ERROR: Function failed: do_compile (see /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041 for further information) ERROR: Task 1470 (/home/vidal/POKY/build062913_dylan/poky/meta-oe/meta-oe/recipes-devtools/python/ python-numpy_1.7.0.bb, do_compile) failed with exit code '1' some thing the text must of strip this Thanks On Mon, Jul 1, 2013 at 6:47 AM, Burton, Ross wrote: > On 1 July 2013 13:37, Edward Vidal wrote: > > This is the error that I get. > > | /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed > > build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o > > build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64 > > > -L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib > > -Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o > > build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so > > | ERROR: Function failed: do_compile (see > > > /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041 > > for further information) > > ERROR: Task 1470 > > > (/home/vidal/POKY/build062913_dylan/poky/meta-oe/meta-oe/recipes-devtools/python/ > python-numpy_1.7.0.bb, > > do_compile) failed with exit code '1' > > That's not the error, all we have there is a build command and bitbake > concluding that there was an error. Because we do parallel make > builds, you'll have to scroll back through the compile log to get the > actual error. Just sending the entire log to a pastebin will be > useful. > > Ross > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fedora 18 CentOS 6.4 yocto difference
On 1 July 2013 14:16, Edward Vidal wrote: > /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed > build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o > build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64 > -L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib > -Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o > build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so > ERROR: Function failed: do_compile (see > /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041 > for further information) That's still not the full log. The full log is at /home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK
On Jul 1, 2013, at 2:16 AM, Ross Burton wrote: > On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote: >> On 2013-06-27 04:06, Ross Burton wrote: >>> The meta-toolchain* recipes are deprecated, so when building >>> meta-toolchain-gmae >>> also build the SDK for core-image-sato. >>> >>> Signed-off-by: Ross Burton >> >> If/when the meta-toolchain recipes go away, how do I create a stand-alone >> toolchain >> derived from Poky/Yocto (which I use all the time!)? pick core-image-minimal. > > The idiom is to pick an image to base the SDK on, and use the > "populate_sdk" task: > > $ bitbake core-image-sato -c populate_sdk > > If you want just the compiler and no userspace, then I'm not sure what > the best solution going forwards is. > > Ross > > ___ > 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] Fwd: Fedora 18 CentOS 6.4 yocto difference
-- Forwarded message -- From: Burton, Ross Date: Mon, Jul 1, 2013 at 8:23 AM Subject: Re: [yocto] Fedora 18 CentOS 6.4 yocto difference To: Edward Vidal On 1 July 2013 14:45, Edward Vidal wrote: > Ross, > I am attaching the recent file. I had to re-run the command since I have rm > work in my local.conf. do you want this to go to the mailing list? Yes, the list is the support contact, not me personally. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: Fedora 18 CentOS 6.4 yocto difference
On 1 July 2013 15:28, Edward Vidal wrote: > > -- Forwarded message -- > From: Burton, Ross > Date: Mon, Jul 1, 2013 at 8:23 AM > Subject: Re: [yocto] Fedora 18 CentOS 6.4 yocto difference > To: Edward Vidal > > > On 1 July 2013 14:45, Edward Vidal wrote: >> Ross, >> I am attaching the recent file. I had to re-run the command since I have >> rm >> work in my local.conf. do you want this to go to the mailing list? > > Yes, the list is the support contact, not me personally. Your attachment didn't survive the forward. I've uploaded the log you sent me directly to http://pastebin.com/uYkyczwb so that everyone else can see. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Recent autobuilder changes
On Mon, Jul 1, 2013 at 1:16 AM, Burton, Ross wrote: > On 30 June 2013 23:40, Flanagan, Elizabeth > wrote: >> This weekend I brought down the autobuilder to implement the new build >> failure email formatter. This *should* provide a bit more detailed >> information in a much easier to read format. Please, let me know of >> any tweaks people might like to see in the message format. > > Much improved! The one thing I'd love to see though is the relevant > branch_* values right at the top, so it's trivial to spot a master vs > MUT vs 1.4.1 build. Ok, let me bang on that today. I still have a few tweaks I have to do still. > > Cheers, > Ross > - > Intel Corporation (UK) Limited > Registered No. 1134945 (England) > Registered Office: Pipers Way, Swindon SN3 1RJ > VAT No: 860 2173 47 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-docs][PATCH] dev-manual: referencing bugzilla issues
On 1 July 2013 02:37, Rifenbark, Scott M wrote: > I got a hold of Saul and confirmed that you are right. I have been entering > these strings incorrectly for a good while now. I have applied your patch to > the tip of the yocto-docs repository and republished in our development area > for the manuals. Great! Thank _you_ :-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky-extras
On Mon, 2013-07-01 at 07:46 +0100, Richard Purdie wrote: > On Sun, 2013-06-30 at 23:18 -0700, Michael Halstead wrote: > > On 06/30/2013 10:44 PM, Darren Hart wrote: > > > On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote: > > > > I can change the name shortly. Is there any reason to keep a read-only > > > > copy available at the current location temporarily? > > > Not really. Unless Bruce is using it in some automated scripts that need > > > to be updated. > > > > > > > The name has been changed. Shall we update the description or is > > "Supplementary metadata layers to extend the Poky core" still > > appropriate? > > We can change it to something like "Supplementary linux-yocto kernel > development metadata" unless Bruce has any better description. Bruce is out this week with limited email access. He isn't terribly picky on naming and that description should work as good as any. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky-extras
I think the name is meta-yocto-kernel-extras. That is what I have pushed to the docs. Scott >-Original Message- >From: Hart, Darren >Sent: Monday, July 01, 2013 10:28 AM >To: Richard Purdie >Cc: Michael Halstead; Bruce Ashfield; Rifenbark, Scott M; yocto; >Zanussi, Tom >Subject: Re: poky-extras > >On Mon, 2013-07-01 at 07:46 +0100, Richard Purdie wrote: >> On Sun, 2013-06-30 at 23:18 -0700, Michael Halstead wrote: >> > On 06/30/2013 10:44 PM, Darren Hart wrote: >> > > On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote: >> > > > I can change the name shortly. Is there any reason to keep a >read-only >> > > > copy available at the current location temporarily? >> > > Not really. Unless Bruce is using it in some automated scripts >that need >> > > to be updated. >> > > >> > >> > The name has been changed. Shall we update the description or is >> > "Supplementary metadata layers to extend the Poky core" still >> > appropriate? >> >> We can change it to something like "Supplementary linux-yocto kernel >> development metadata" unless Bruce has any better description. > >Bruce is out this week with limited email access. He isn't terribly >picky on naming and that description should work as good as any. > >-- >Darren Hart >Intel Open Source Technology Center >Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] FW: Yocto Project Technical Team Meeting
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="Liu, Song":MAILTO:song@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yocto@yoct oproject.org:MAILTO:yocto@yoctoproject.org DESCRIPTION;LANGUAGE=en-US:\n\n-Original Appointment-\nFrom: Liu\, Song\nSent: Wednesday\, June 19\, 2013 2:44 PM\nTo: Liu\, Song\; 'Anders D arander'\; Barros Pena\, Belen\; Bodke\, Kishore K\; 'Bruce Ashfield'\; 'D aniel Cauchy'\; 'deVries\, Alex'\; 'Dixon\, Brad'\; Dmytriyenko\, Denys\; Erway\, Tracey M\; Flanagan\, Elizabeth\; Hart\, Darren\; 'Hatle\, Mark'\; 'Jeremy Puhlman'\; Kridner\, Jason\; 'lieu...@windriver.com'\; Lock\, Jos hua\; 'McCombe\, Kevin'\; Moeller\, Thorsten\; 'Sanjay Raina'\; Osier-mixo n\, Jeffrey\; 'Polk\, Jeffrey'\; Purdie\, Richard\; 'Ranslam\, Rob'\; Saxe na\, Rahul\; Stewart\, David C\; Wold\, Saul\; Zanussi\, Tom\; Zhang\, Jes sica\; Rifenbark\, Scott M\; 'Hudson\, Sean'\; Serban\, Laurentiu\; Petris or\, Ileana\; Damian\, Alexandru\; Burton\, Ross\; Mueller\, Robert\; Arce Moreno\, Abraham\; 'Ravi Vompolu'\; 'Sadiq\, Irfan'\; Santana Lopez\, Mar io A\; Calles Palacios\, Osvaldo\; Patel\, Keyur R\; 'achau...@mvista.com' \; Popa\, Valentin\; Moses\, Fred\; Iorga\, Cristian\; Palalau\, Alexandru X\; 'Butler\, Paul'\; Mirea\, Viorel\; Kamble\, Nitin A\; Szankin\, Maciej \; Moisan\, Radu\; Grigoropol\, IoanaX\; Olivia Salisbury\; 'Chris Kaminsk i'\; 'Maupin\, Chase'\; Georgescu\, Alexandru C\; Gavaz\, Ionut A\; Prutea nu\, Codrin C\; Letnes\, Thaddeus C\; Ong\, Boon Leong\; Seow\, Chen Yong\ ; Haw\, Foo Chien\nCc: Stoicescu\, CorneliuX\; Chris Kaminski\nSubject: Yo cto Project Technical Team Meeting\nWhen: Occurs every Tuesday effective 6 /25/2013 until 12/31/2013 from 8:00 AM to 9:00 AM (UTC-08:00) Pacific Time (US & Canada).\nWhere: Bridge Info Enclosed\n\n\nWe encourage people atte nding the meeting to logon the Yocto IRC chancel during the meeting (optio nal):\n\nYocto IRC: http://webchat.freenode.net/?channels=#yocto\nIRC Tuto rial: http://www.irchelp.org/irchelp/irctutorial.html\n\nConference detail s\nConference name:Yocto Project Technical Team\nConference date/s tart time: Tue Jun 25\, 2013 at 11:00 AM Eastern Daylight Time (GMT-04 00)\nParticipants: 30\nDuration: 60 minutes\nParticipant passcode: 42001078\nDial-in number: 1.972.995.\nUS Toll Free number:1.877 .561.6828\nBlackBerry users\, click this link to join your conference as a participant: 1.972.995.x42001078#\nDepending on where you are dialing from\, either your BlackBerry will pause and enter the passco de automatically or you will be prompted to click again to dial the passco de.\n\n\nLocal and Global Access Numbers\n\n\n\n\nCountry\nDial-in number\ n\nAustralia:\n1800 636 843\n\nCzech Republic:\n242 430 350\n\nChina (Beij ing):\nFrom office dial 8-995 or 8784277\nBeijing Out of Office dial 5 878 4277\n\nChina (Shanghai):\nFrom office dial 8-995 or 3073322\nShan ghai Out of Office dial 2307 3322\n\nChina (Shenzen):\nFrom office dial 8- 995 or 6007877\nShenzen Out of Office dial 2600 7877\n\nChina (Other C ities):\nFrom IP phone dial 8-995\nOther cities - Non IP phone dial 02 1-23073322\n\nDenmark:\n8060 1400\n\nFinland:\n09 41333477\n\nFrance:\n049 7 275888\n\nGermany:\n08161 803232\n\nHolland:\n030 2417490\n\nIndia:\nBSN L subscribers use 1800 425 9996 (Toll Free)\nAirtel subscribers use 0008 0 09 861 212 (Toll Free)\nFrom TI Campus use 8995\nOthers use 2509 9555 (Landline within Bangalore) or\n80 2509 9555 (Outside Bangalore)\n\nIsrael :\n09 790 6715\n\nItaly:\n039 69061234 (039 is local city code not country code)\n\nJapan:\nFrom TI Campus use 8 995 \nOutside TI use 03 4331 37 77\n\nMalaysia:\nFrom IP phone dial 2643799\nFrom Kuala Lumpur dial 4264 3 799\nOutside Kuala Lumpur dial (03)4264 3799\n\nNorway:\n2 295 8744\n\nPhi lippines:\nFrom Baguio City use 4471177\nFrom Metro Manila area use 870247 7\n\nSingapore:\nFrom IP phone dial 3894777\nOutside TI use 6389 4777\n\nS outh Korea:\nFrom IP phone dial 5606998\nFrom Seoul dial 5606998\nOutside Seoul dial (02)5606998\n\nSweden:\n08 58755577\n\nTaiwan:\nFrom IP phone d ial 1363\nFrom Taipei dial 2241 1363\nOutside Taipei dial (02)2241 1363\n\ nTurkey:\nLandline Only dial 0811 288 0001\nthen enter 877 633 1123\n\nUK: \n01908 355599\n\nUS:\n972 995 or 1877 561 6828\n\n\nRecurring confer ences\nFirst scheduled conference: Tue Jun 25\, 2013\nRecurrence frequ ency: Weekly - Every 1 week(s) on Tuesday\nRecurrence ends:
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, July 02, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Agenda: * Opens collection - 5 min (Song) * Yocto 1.5 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.5_Status * Yocto Project 1.5 QA plan review - 20 min (AlexG/MihaiL) https://wiki.yoctoproject.org/wiki/1.5_Overall_Test_Plan * SWAT team rotation: Radu M -> Constantin M * Opens - 10 min * Team Sharing - 15 min We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference details Conference name:Yocto Project Technical Team Conference date/start time: Tue Jun 25, 2013 at 11:00 AM Eastern Daylight Time (GMT-0400) Participants: 30 Duration: 60 minutes Participant passcode: 42001078 Dial-in number: 1.972.995. US Toll Free number:1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.x42001078# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): >From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): >From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): >From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): >From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) >From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: >From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: >From IP phone dial 2643799 >From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: >From Baguio City use 4471177 >From Metro Manila area use 8702477 Singapore: >From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: >From IP phone dial 5606998 >From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: >From IP phone dial 1363 >From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01908 355599 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 25, 2013 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends:End after 52 occurrences ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
