date:20180226

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-02-26 Thread Burton, Ross

Running your own feed for personal use is trivial, just point lighttpd or
any other HTTP server at the deploy/deb directory on your build machine.
If you set PACKAGE_FEED_URLS in your local.conf to the URL of the server
then future images will contain a pre-populated sources.list.

However the only relationship between your Yocto image and Rapsian is that
they both use Linux and APT. You can't just re-use packages from Raspian
(just like you wouldn't expect to re-use packages from Fedora), so if
that's your goal then you should just use Raspian.

Ross

On 25 February 2018 at 13:38, Laigui Qin  wrote:

> Hi Everyone,
>
> I am building the GNU Linux with Yocto for Raspberry Pi using
> meta-raspberrypi. Everything is good (with help of google search and yocto
> manual) until I added apt support to the image. As I am a little confused
> which Repository URL I should put in the sources.list, I tried the Raspbian
> repository. However, when I do apt-get upgrade I got following error which
> is not expected. Any idea on this effort?
>
> BR,
> Mike
>
> root@raspberrypi-cm3:~# sudo apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages have been kept back:
>   base-files cpp diffutils g++ gcc git initscripts libcap2 libgcc1
> libgmp10 libsysfs2 libusb-1.0-0 libwbclient0 netcat ntp procps samba-common
> usbutils
> The following packages will be upgraded:
>   busybox ethtool sysfsutils
> 3 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
> Need to get 562 kB of archives.
> After this operation, 1114 kB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 http://archive.raspbian.org/raspbian wheezy/main armhf busybox
> armhf 1:1.20.0-7 [438 kB]
> Get:2 http://archive.raspbian.org/raspbian wheezy/main armhf ethtool
> armhf 1:3.4.2-1 [98.7 kB]
> Get:3 http://archive.raspbian.org/raspbian wheezy/main armhf sysfsutils
> armhf 2.1.0+repack-2 [24.5 kB]
> Fetched 562 kB in 5s (96.0 kB/s)
> (Reading database ... 16225 files and directories currently installed.)
> Preparing to unpack .../busybox_1%3a1.20.0-7_armhf.deb ...
> Unpacking busybox (1:1.20.0-7) over (1.24.1-r0) ...
> dpkg-deb (subprocess): unable to execute tar (tar): No such file or
> directory
> *dpkg-deb:* *error:* subprocess tar returned error exit status 2
> *dpkg:* error processing archive 
> /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb
> (--unpack):
>  subprocess dpkg-deb --control returned error exit status 2
> dpkg-deb (subprocess): unable to execute tar (tar): No such file or
> directory
> *dpkg-deb:* *error:* subprocess tar returned error exit status 2
> *dpkg:* error processing archive /var/cache/apt/archives/
> sysfsutils_2.1.0+repack-2_armhf.deb (--unpack):
>  subprocess dpkg-deb --control returned error exit status 2
> Errors were encountered while processing:
>  /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb
>  /var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
>
>
> --
> ___
> 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] Problem in the building phase - Yocto 2.4.1 for Siemens IoT 2040 (Intel Quark)

2018-02-26 Thread Maxin B. John

Hi,

On Sat, Feb 24, 2018 at 12:11:56PM -0800, Stephano Cetola wrote:
> On 2/22/18 3:59 AM, Pulizzotto Alessio (COMAU) wrote:
> > Hello,
> >
> > I’m writing you because I have some problems with the building of an
> > 2.4.1 image of the Yocto.
> >
> > I am using a Siemens IoT 2040 hardware witch have an intel quark cpu.
> > 
> > My error is the follow, in the “bitbake name-image”:
> > 
> > “ExpansionError during parsing
> > ***/poky/meta-java/recipies-extended/xmlpull/xmlpull_1.1.3.4c.bb”
> > 
> > And at the end:
> > 
> > “module bb.data has no attribute ‘getVar’”
> > 

Tried building xmlpull for qemux86 with oe-core master branch.

meta-java:
master branch
commit: fbe0b0eb30d93f5fa2101fb015f20c1dc118b4a6

It builds fine. Could you build with "rocko" branch of meta-java
and see if that fixes this error ?

> I am currently building for a product using Quark + Java running YP
> 2.4.1. Here are the SHAs that are working for me:
> 
> meta-yocto-bsp
> yocto-2.4.1
> c2b641c8a0c4fd71fcb477d788a740c2c26cddce
> 
> meta-intel
> 8.0-rocko-2.4
> d68dda959b5bf6f90aa8e5c2f027be324bb68e14
> 
> meta-java
> master
> 03e35bf64f97980652ac532cca0ea96e730a551c
> 
> Cheers,
> Stephano
>

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

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-02-26 Thread Laigui Qin

Hello Johnny,


Thanks for the reply.
Yes, I know that's not a good idea now.
I would like to think there is a well maintained Yocto/Poky repository 
somewhere in the world like the debian/Raspbian deb source to leverage (build 
and maintain my own repo is not my purpose.) Looks like there is not such repo 
available...
I do notice there is a Yocto subproject called "meta-debian", which try to 
leverage the debian repo. But not sure whether it works well without 
limitation...


BR,
Mike






At 2018-02-26 14:20:15, "Johnny R Cash"  wrote:

Greetings.
If i understand you correctly you configured your Yocto/Poky OS to try to fetch 
updates from Raspbian OS.
You would need to configure Yocto/Poky to update from a Yocto/Poky repository. 
As with using Yocto you probably are defining your own, that would have to be 
your own repository URL.
BR

On 25.02.2018 14:38, Laigui Qin wrote:

Hi Everyone,


I am building the GNU Linux with Yocto for Raspberry Pi using meta-raspberrypi. 
Everything is good (with help of google search and yocto manual) until I added 
apt support to the image. As I am a little confused which Repository URL I 
should put in the sources.list, I tried the Raspbian repository. However, when 
I do apt-get upgrade I got following error which is not expected. Any idea on 
this effort?


BR,
Mike


root@raspberrypi-cm3:~# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  base-files cpp diffutils g++ gcc git initscripts libcap2 libgcc1 libgmp10 
libsysfs2 libusb-1.0-0 libwbclient0 netcat ntp procps samba-common usbutils
The following packages will be upgraded:
  busybox ethtool sysfsutils
3 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
Need to get 562 kB of archives.
After this operation, 1114 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.raspbian.org/raspbian wheezy/main armhf busybox armhf 
1:1.20.0-7 [438 kB]
Get:2 http://archive.raspbian.org/raspbian wheezy/main armhf ethtool armhf 
1:3.4.2-1 [98.7 kB]
Get:3 http://archive.raspbian.org/raspbian wheezy/main armhf sysfsutils armhf 
2.1.0+repack-2 [24.5 kB]
Fetched 562 kB in 5s (96.0 kB/s)   
(Reading database ... 16225 files and directories currently installed.)
Preparing to unpack .../busybox_1%3a1.20.0-7_armhf.deb ...
Unpacking busybox (1:1.20.0-7) over (1.24.1-r0) ...
dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
dpkg-deb: error: subprocess tar returned error exit status 2
dpkg: error processing archive 
/var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
dpkg-deb: error: subprocess tar returned error exit status 2
dpkg: error processing archive 
/var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb
 /var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)




 






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

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-02-26 Thread Laigui Qin

Hello Josef,


Thanks for the guide.
I think choice 1 is best solution for my situation based on the context.


BR,
Mike



At 2018-02-26 15:38:40, "Josef Holzmayr"  wrote:
>Hello!
>
>On Sun, Feb 25, 2018 at 09:38:52PM +0800, Laigui Qin wrote:
>> I am building the GNU Linux with Yocto for Raspberry Pi using 
>> meta-raspberrypi. Everything is good (with help of google search and yocto 
>> manual) until I added apt support to the image. As I am a little confused 
>> which Repository URL I should put in the sources.list, I tried the Raspbian 
>> repository. However, when I do apt-get upgrade I got following error which 
>> is not expected. Any idea on this effort?
>
>Unless you are planning to run your own repository server: none. There
>is certainly support for doing that, look for topic on "package feeds"
>in the Yocto documentation.
>
>Your snippet below looks like you are trying to use the raspbian
>repositories, which certainly won't work. You have to understand that
>what you have built is *NOT* a replacement for a raspbian installation
>that will just fill in - it is a whole separated, custom distribution
>and in no way related to any package repository thats out there. So if
>you actually want to use those, then you have also to use their base
>distribution.
>
>If you want to stick with Yocto, your two choices are:
>- just include everything you need in the build. (thats the common one)
>- run a custom package feed server (can be done, but probably you're
>  better off with already existing solutions then.
>
>Greetz Joe
>
>> 
>> root@raspberrypi-cm3:~# sudo apt-get upgrade
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> Calculating upgrade... Done
>> The following packages have been kept back:
>>   base-files cpp diffutils g++ gcc git initscripts libcap2 libgcc1 libgmp10 
>> libsysfs2 libusb-1.0-0 libwbclient0 netcat ntp procps samba-common usbutils
>> The following packages will be upgraded:
>>   busybox ethtool sysfsutils
>> 3 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
>> Need to get 562 kB of archives.
>> After this operation, 1114 kB of additional disk space will be used.
>> Do you want to continue? [Y/n] 
>> Get:1 http://archive.raspbian.org/raspbian wheezy/main armhf busybox armhf 
>> 1:1.20.0-7 [438 kB]
>> Get:2 http://archive.raspbian.org/raspbian wheezy/main armhf ethtool armhf 
>> 1:3.4.2-1 [98.7 kB]
>> Get:3 http://archive.raspbian.org/raspbian wheezy/main armhf sysfsutils 
>> armhf 2.1.0+repack-2 [24.5 kB]
>> Fetched 562 kB in 5s (96.0 kB/s)   
>> (Reading database ... 16225 files and directories currently installed.)
>> Preparing to unpack .../busybox_1%3a1.20.0-7_armhf.deb ...
>> Unpacking busybox (1:1.20.0-7) over (1.24.1-r0) ...
>> dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
>> dpkg-deb: error: subprocess tar returned error exit status 2
>> dpkg: error processing archive 
>> /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb (--unpack):
>>  subprocess dpkg-deb --control returned error exit status 2
>> dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
>> dpkg-deb: error: subprocess tar returned error exit status 2
>> dpkg: error processing archive 
>> /var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb (--unpack):
>>  subprocess dpkg-deb --control returned error exit status 2
>> Errors were encountered while processing:
>>  /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb
>>  /var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>-- 
>———
>Josef Holzmayr
>Software Developer Embedded Systems
>
>Tel: +49 8444 9204-48
>Fax: +49 8444 9204-50
>
>R-S-I Elektrotechnik GmbH & Co. KG
>Woelkestrasse 11
>D-85301 Schweitenkirchen
>www.rsi-elektrotechnik.de
>———
>Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
>Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
>Ust-IdNr: DE 128592548 
>
>_
>Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
>Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
>USt-IdNr.: DE 128592548
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-02-26 Thread Laigui Qin

Thanks Ross. got your point on Raspbian package difference. and 
PACKAGE_FEED_URLS attribute is useful for me. -Mike




At 2018-02-26 18:16:48, "Burton, Ross"  wrote:

Running your own feed for personal use is trivial, just point lighttpd or any 
other HTTP server at the deploy/deb directory on your build machine.  If you 
set PACKAGE_FEED_URLS in your local.conf to the URL of the server then future 
images will contain a pre-populated sources.list.


However the only relationship between your Yocto image and Rapsian is that they 
both use Linux and APT. You can't just re-use packages from Raspian (just like 
you wouldn't expect to re-use packages from Fedora), so if that's your goal 
then you should just use Raspian.


Ross


On 25 February 2018 at 13:38, Laigui Qin  wrote:

Hi Everyone,


I am building the GNU Linux with Yocto for Raspberry Pi using meta-raspberrypi. 
Everything is good (with help of google search and yocto manual) until I added 
apt support to the image. As I am a little confused which Repository URL I 
should put in the sources.list, I tried the Raspbian repository. However, when 
I do apt-get upgrade I got following error which is not expected. Any idea on 
this effort?


BR,
Mike


root@raspberrypi-cm3:~# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  base-files cpp diffutils g++ gcc git initscripts libcap2 libgcc1 libgmp10 
libsysfs2 libusb-1.0-0 libwbclient0 netcat ntp procps samba-common usbutils
The following packages will be upgraded:
  busybox ethtool sysfsutils
3 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
Need to get 562 kB of archives.
After this operation, 1114 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.raspbian.org/raspbian wheezy/main armhf busybox armhf 
1:1.20.0-7 [438 kB]
Get:2 http://archive.raspbian.org/raspbian wheezy/main armhf ethtool armhf 
1:3.4.2-1 [98.7 kB]
Get:3 http://archive.raspbian.org/raspbian wheezy/main armhf sysfsutils armhf 
2.1.0+repack-2 [24.5 kB]
Fetched 562 kB in 5s (96.0 kB/s)   
(Reading database ... 16225 files and directories currently installed.)
Preparing to unpack .../busybox_1%3a1.20.0-7_armhf.deb ...
Unpacking busybox (1:1.20.0-7) over (1.24.1-r0) ...
dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
dpkg-deb: error: subprocess tar returned error exit status 2
dpkg: error processing archive 
/var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
dpkg-deb (subprocess): unable to execute tar (tar): No such file or directory
dpkg-deb: error: subprocess tar returned error exit status 2
dpkg: error processing archive 
/var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb (--unpack):
 subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/ethtool_1%3a3.4.2-1_armhf.deb
 /var/cache/apt/archives/sysfsutils_2.1.0+repack-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)




 


--
___
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] [PATCH][meta-mingw] binutils: generalise version wildcard

2018-02-26 Thread Ross Burton

Don't be overly specific by demanding 2.2%, 2.% is sufficient as this bbappend
simply changes some options.

Signed-off-by: Ross Burton 
---
 ...-cross-canadian_2.2%.bbappend => binutils-cross-canadian_2.%.bbappend} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-devtools/binutils/{binutils-cross-canadian_2.2%.bbappend => 
binutils-cross-canadian_2.%.bbappend} (100%)

diff --git a/recipes-devtools/binutils/binutils-cross-canadian_2.2%.bbappend 
b/recipes-devtools/binutils/binutils-cross-canadian_2.%.bbappend
similarity index 100%
rename from recipes-devtools/binutils/binutils-cross-canadian_2.2%.bbappend
rename to recipes-devtools/binutils/binutils-cross-canadian_2.%.bbappend
-- 
2.11.0

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

[yocto] Yocto Project Status WW09’18

2018-02-26 Thread Jordan, Robin L

Current Dev Position: YP 2.5 M3 development

Next Deadline: YP 2.5 M3 cut off was 2/19/18

*** FEATURE FREEZE for 2.5 has passed ***


SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018

SWAT team rotation: Maxin -> Rebecca on March 2, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   YP 2.5 M2 is through QA and likely to be released early this week.
  *   YP 2.2.3 is through QA and likely to be released early this week.
  *   YP 2.4.2 rc2 was successfully built and is undergoing QA.
  *   YP 2.5 M3 is feature freeze. After discussions with various people we 
concluded that we need:
 *   the 2.27 glibc upgrade
 *   kernel-devsrc size changes
 *   to resolve some of the outstanding pseudo bugs
 *   to resolve the multilib SDK patch series
 *   the package feed filtering patch series (the multilib SDK series 
depends on it)
 *   image EFI configuration rework
  *   We plan to defer:
 *   pkg-conf vs. pkgconfig issues/discussion
 *   profile guided optimisation for python (patch series)
 *   oe-selftest parallelization
  *   We’re continuing to work on the autobuilder changes and for various 
reasons (inc. changes in people).  We would be in much better shape to switch 
to the new codebase before release, rather than waiting until early 2.6 to pick 
this work up again by which time we’d have lost people and context. If we are 
to switch, we need to build M3 with the new infrastructure. We’ll have to make 
a decision on whether we do this during this week.


Planned upcoming dot releases:

YP 2.4.2 (Rocko) is currently in QA 82% complete.   See: 
https://wiki.yoctoproject.org/wiki/2.4_QA_Status

YP 2.3.4 (Pyro) will be built when we figure out gcc backports.

YP 2.2.3 (Morty) rc2 has passed QA and is being prepared for release

YP 2.2.4 (Morty) will be built when we figure out gcc backports.


Key YP 2.5 Dates are:

YP 2.5 M2 has passed QA and is being prepared for release.

YP 2.5 M3 is in feature freeze.  See status above.

YP 2.5 M3 release of 3/2/18

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2646 (last week   2648)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Robin Jordan
Yocto Project Program Manager
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW09’18

2018-02-26 Thread akuster808



On 02/26/2018 08:13 AM, Jordan, Robin L wrote:
>
> Current Dev Position: YP 2.5 M3 development
>
> Next Deadline: YP 2.5 M3 cut off was 2/19/18
>
> *** FEATURE FREEZE for 2.5 has passed ***
>
>  
>
> SWAT team rotation: Stephano -> Maxin John on Feb. 23, 2018
>
> SWAT team rotation: Maxin -> Rebecca on March 2, 2018
>
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>  
>
> Key Status/Updates:
>
>   * YP 2.5 M2 is through QA and likely to be released early this week.
>   * YP 2.2.3 is through QA and likely to be released early this week.
>   * YP 2.4.2 rc2 was successfully built and is undergoing QA.
>   * YP 2.5 M3 is feature freeze. After discussions with various people
> we concluded that we need:
>   o the 2.27 glibc upgrade
>   o kernel-devsrc size changes
>   o to resolve some of the outstanding pseudo bugs
>   o to resolve the multilib SDK patch series
>   o the package feed filtering patch series (the multilib SDK
> series depends on it)
>   o image EFI configuration rework
>   * We plan to defer:
>   o pkg-conf vs. pkgconfig issues/discussion
>   o profile guided optimisation for python (patch series)
>   o oe-selftest parallelization
>   * We’re continuing to work on the autobuilder changes and for
> various reasons (inc. changes in people).  We would be in much
> better shape to switch to the new codebase before release, rather
> than waiting until early 2.6 to pick this work up again by which
> time we’d have lost people and context. If we are to switch, we
> need to build M3 with the new infrastructure. We’ll have to make a
> decision on whether we do this during this week.
>

I recommend updating to new code base on the old cluster for debug. We
can fallback to the .io and/or use them in parallel.

Will the new code base work on stable branches?

>  *
>
>  
>
> Planned upcoming dot releases:
>
> YP 2.4.2 (Rocko) is currently in QA 82% complete.   See:
> https://wiki.yoctoproject.org/wiki/2.4_QA_Status
>
stable/rocko-next: clean build last night

> YP 2.3.4 (Pyro) will be built when we figure out gcc backports.
>
stable/pyro-next: Mostly clean. GCC update pulled out for V2. V2 not
merged back.


> YP 2.2.3 (Morty) rc2 has passed QA and is being prepared for release
>
> YP 2.2.4 (Morty) will be built when we figure out gcc backports.
>
stable/morty-next: Getting cleaner. recommend updating to version in pyro.

- armin
>
>  
>
> Key YP 2.5 Dates are:
>
> YP 2.5 M2 has passed QA and is being prepared for release.
>
> YP 2.5 M3 is in feature freeze.  See status above.
>
> YP 2.5 M3 release of 3/2/18
>
> YP 2.5 M4 cut off of 4/2/18
>
> YP 2.5 M4 release of 4/27/18
>
>  
>
> Tracking Metrics:
>
>     WDD 2646 (last week   2648)
>
> (https://wiki.yoctoproject.org/charts/combo.html)
>
>  
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
>
>  
>
> The Status reports are now stored on the wiki at:
> https://wiki.yoctoproject.org/wiki/Weekly_Status
>
>  
>
> [If anyone has suggestions for other information you’d like to see on
> this weekly status update, let us know!]
>
>  
>
> Robin Jordan
>
> Yocto Project Program Manager
>
>
>

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

[yocto] Looking for an Embedded Developer using Yocto

2018-02-26 Thread Stephen Perry

I am looking for an Linux Embedded Developer with experience with Yocto working 
on Network Devices for a full time role with a company in Toronto Canada.

Please feel free to reach out to me for more details if interested.

Thanks,

Stephen

Stephen Perry, Sr. I.T. Recruiter  | TAL Technology
69 Yonge Street, Suite 1100 | Toronto, Ontario M5E 1K3  |Phone:  416.599.1825 
ext. 223
www.talgroup.net  | Connect with us on 
Facebook, 
Twitter & 
LinkedIn

[cid:image001.png@01D38551.1058B310]

TAL Group is proud to be a CAMSC Certified Supplier in 2018. #DiversityMatters 
in the workplace, and we commit to creating opportunities for minority and 
aboriginal owned businesses, suppliers and jobseekers across Canada.



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

[yocto] ksize.py not working?

2018-02-26 Thread Jerry Lian

I want to check/analyze kernel image size, and I found:
* ksum.py works as expected!
* however, ksize.py produces results of "all zeros".

Anybody know the problem and how to fix it?

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

[yocto] How to pass volume size to ubinize when building ubi file system

2018-02-26 Thread Bejar-Colonia, Carlos

Hello Yocto Team,

I need to set the "vol_size" used by ubinize, when building a ubi filesystem.
Looks like, by default, Yocto doesn't set the vol_size during the build.

Only these params are set in poky/meta/classes/image_types.bbclass

echo vol_id=0 >> ubinize${vname}-${IMAGE_NAME}.cfg
echo vol_type=dynamic >> ubinize${vname}-${IMAGE_NAME}.cfg
echo vol_name=${UBI_VOLNAME} >> ubinize${vname}-${IMAGE_NAME}.cfg
echo vol_flags=autoresize >> ubinize${vname}-${IMAGE_NAME}.cfg
mkfs.ubifs -r ${IMAGE_ROOTFS} -o 
${IMGDEPLOYDIR}/${IMAGE_NAME}${vname}${IMAGE_NAME_SUFFIX}.ubifs ${mkubifs_args}

Is there a way to set the vol_size without modifying image_types.bbclass?

Thanks,
Carlos


The information contained in this message may be confidential and legally 
protected under applicable law. The message is intended solely for the 
addressee(s). If you are not the intended recipient, you are hereby notified 
that any use, forwarding, dissemination, or reproduction of this message is 
strictly prohibited and may be unlawful. If you are not the intended recipient, 
please contact the sender by return e-mail and destroy all copies of the 
original message.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-gplv2][PATCH] gnutls: update 3.3.28 -> 3.3.29

2018-02-26 Thread Andre McCurdy

* Version 3.3.29 (released 2018-02-16)

** libgnutls: Fixed issue which caused 1-byte handshake fragments to be refused.
   Reported by Balázs Kéri.

** libgnutls: Fixed interoperability issue with openssl when safe renegotiation 
was
   used. Resolves gitlab issue #259.

** libgnutls: Use readdir() instead of readdir_r internally. The latter
   is deprecated and on our use we don't need readdir() to be thread safe
   (which it is in most common platforms).

** libgnutls: require strict DER encoding for certificates, OCSP requests, 
private
   keys, CRLs and certificate requests.  This backports the already default 
behavior
   from the 3.5.x branch, in order to reduce issues due to the complexity of 
BER rules.

** libgnutls: Addressed issue in the AES-CBC acceleration under ssse3 (patch by
   Vitezslav Cizek).

** libgnutls: Addressed issue in the accelerated code which may affect 
interoperability
   with versions of nettle > 3.4.

** p11tool: Fixed issue preventing the deletion of objects in batch mode.

** p11tool: Mark all generated objects as sensitive by default.

** API and ABI modifications:
No changes since last version.

Signed-off-by: Andre McCurdy 
---
 recipes-support/gnutls/gnutls_3.3.28.bb | 8 
 recipes-support/gnutls/gnutls_3.3.29.bb | 8 
 2 files changed, 8 insertions(+), 8 deletions(-)
 delete mode 100644 recipes-support/gnutls/gnutls_3.3.28.bb
 create mode 100644 recipes-support/gnutls/gnutls_3.3.29.bb

diff --git a/recipes-support/gnutls/gnutls_3.3.28.bb 
b/recipes-support/gnutls/gnutls_3.3.28.bb
deleted file mode 100644
index 1b23369..000
--- a/recipes-support/gnutls/gnutls_3.3.28.bb
+++ /dev/null
@@ -1,8 +0,0 @@
-require gnutls.inc
-
-SRC_URI += " \
-file://configure.ac-fix-sed-command.patch \
-file://use-pkg-config-to-locate-zlib.patch \
-"
-SRC_URI[md5sum] = "e19718d97cee5279edf3f3b9318f926c"
-SRC_URI[sha256sum] = 
"608f63441abc209c5bd5f61e35f2b6128c22e06fa2ad6248a08d8a643feeb807"
diff --git a/recipes-support/gnutls/gnutls_3.3.29.bb 
b/recipes-support/gnutls/gnutls_3.3.29.bb
new file mode 100644
index 000..21099eb
--- /dev/null
+++ b/recipes-support/gnutls/gnutls_3.3.29.bb
@@ -0,0 +1,8 @@
+require gnutls.inc
+
+SRC_URI += " \
+file://configure.ac-fix-sed-command.patch \
+file://use-pkg-config-to-locate-zlib.patch \
+"
+SRC_URI[md5sum] = "de7a58232d42b1d71baf38a06dc34412"
+SRC_URI[sha256sum] = 
"fa9d13f1bc35b81fac85152906b8d4950f4f5a90d76d5b406c1167728770c94a"
-- 
1.9.1

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

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

Re: [yocto] Problem in the building phase - Yocto 2.4.1 for Siemens IoT 2040 (Intel Quark)

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

[yocto] [PATCH][meta-mingw] binutils: generalise version wildcard

[yocto] Yocto Project Status WW09’18

Re: [yocto] Yocto Project Status WW09’18

[yocto] Looking for an Embedded Developer using Yocto

[yocto] ksize.py not working?

[yocto] How to pass volume size to ubinize when building ubi file system

[yocto] [meta-gplv2][PATCH] gnutls: update 3.3.28 -> 3.3.29

12 matches

Site Navigation

Mail list logo

Footer information