Re: [yocto] [meta-mingw][PATCH] bzip2: Update to 1.0.7

2019-07-02 Thread Adrian Bunk 
On Tue, Jul 02, 2019 at 03:21:32PM -0500, Joshua Watt wrote:
> Updates bzip2 to version 1.0.7 to match master in oe-core. The patch to
> change the path separator was properly upstreamed and hopefully will no
> longer be necessary going forward.
>...
> +--- a/bzip2.c
>  b/bzip2.c
> +@@ -128,7 +128,7 @@
> + #if BZ_LCCWIN32
> + #   include 
> + #   include 
> +-#   include 
> ++#   include 
>...

Why is this a bbappend at all?

This should have been part of the package in oe-core from the beginning,
and could still be added there right now.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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

[yocto] [meta-mingw][PATCH] bzip2: Update to 1.0.7

2019-07-02 Thread Joshua Watt 
Updates bzip2 to version 1.0.7 to match master in oe-core. The patch to
change the path separator was properly upstreamed and hopefully will no
longer be necessary going forward.

Signed-off-by: Joshua Watt 
---
 .../0001-Fix-include-path-separator.patch | 33 +++
 recipes-extended/bzip2/bzip2/fix.patch| 13 
 recipes-extended/bzip2/bzip2_1.0.6.bbappend   |  4 ---
 recipes-extended/bzip2/bzip2_1.0.7.bbappend   |  4 +++
 4 files changed, 37 insertions(+), 17 deletions(-)
 create mode 100644 
recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
 delete mode 100644 recipes-extended/bzip2/bzip2/fix.patch
 delete mode 100644 recipes-extended/bzip2/bzip2_1.0.6.bbappend
 create mode 100644 recipes-extended/bzip2/bzip2_1.0.7.bbappend

diff --git a/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch 
b/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
new file mode 100644
index 000..4c43b7a
--- /dev/null
+++ b/recipes-extended/bzip2/bzip2/0001-Fix-include-path-separator.patch
@@ -0,0 +1,33 @@
+From 84c8769b52c63cce8a8a413e5fcbad1a65681d46 Mon Sep 17 00:00:00 2001
+From: Joshua Watt 
+Date: Tue, 2 Jul 2019 13:06:30 -0500
+Subject: [PATCH] Fix include path separator
+
+Changes the include path separator for Windows builds to use "/" instead
+of "\". Windows has no problems with using a forward slash as a path
+separator, but using a backslash causes problems when attempting to
+cross compile for other platforms (for example, when trying to cross
+compile for MinGW from Linux).
+
+Signed-off-by: Joshua Watt 
+Upstream-Status: Submitted 
[https://sourceware.org/ml/bzip2-devel/2019-q3/msg4.html]
+---
+ bzip2.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/bzip2.c b/bzip2.c
+index e362c65..be3b3be 100644
+--- a/bzip2.c
 b/bzip2.c
+@@ -128,7 +128,7 @@
+ #if BZ_LCCWIN32
+ #   include 
+ #   include 
+-#   include 
++#   include 
+ 
+ #   define NORETURN   /**/
+ #   define PATH_SEP   '\\'
+-- 
+2.21.0
+
diff --git a/recipes-extended/bzip2/bzip2/fix.patch 
b/recipes-extended/bzip2/bzip2/fix.patch
deleted file mode 100644
index a366a5d..000
--- a/recipes-extended/bzip2/bzip2/fix.patch
+++ /dev/null
@@ -1,13 +0,0 @@
-Index: bzip2-1.0.6/bzip2.c
-===
 bzip2-1.0.6.orig/bzip2.c   2010-09-10 23:04:53.0 +
-+++ bzip2-1.0.6/bzip2.c2013-08-13 10:30:15.596120522 +
-@@ -128,7 +128,7 @@
- #if BZ_LCCWIN32
- #   include 
- #   include 
--#   include 
-+#   include 
- 
- #   define NORETURN   /**/
- #   define PATH_SEP   '\\'
diff --git a/recipes-extended/bzip2/bzip2_1.0.6.bbappend 
b/recipes-extended/bzip2/bzip2_1.0.6.bbappend
deleted file mode 100644
index 882147c..000
--- a/recipes-extended/bzip2/bzip2_1.0.6.bbappend
+++ /dev/null
@@ -1,4 +0,0 @@
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI_append_mingw32 = " file://fix.patch"
\ No newline at end of file
diff --git a/recipes-extended/bzip2/bzip2_1.0.7.bbappend 
b/recipes-extended/bzip2/bzip2_1.0.7.bbappend
new file mode 100644
index 000..3cc4b01
--- /dev/null
+++ b/recipes-extended/bzip2/bzip2_1.0.7.bbappend
@@ -0,0 +1,4 @@
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI_append_mingw32 = " file://0001-Fix-include-path-separator.patch"
-- 
2.21.0

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

[yocto] Yocto Project Status WW27'19

2019-07-02 Thread sjolley.yp.pm 
Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Chen
*   SWAT team rotation: Chen -> Armin on July 5, 2019
*   SWAT team rotation: Armin -> Amanda on July 12, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 11th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 rc1 is in QA
*   Emails about the mailing list transition are being prepared and we
now have a plan to move forward. The list addresses will need to change,
archive URLs should remain available.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   There is a discussion on the mailing list about reproducibility in
the project, please respond there if you have opinions.
*   The autobuilder is continuing to see NFS glitches, we know how to
unblock them but aren't sure of the cause at present.
*   There is a performance issue with the autobuilder UI we've been
debugging where build cancellation in particular locks the controller up for
several minutes. Switching the database backend from sqlite to mysql after
advice from upstream unfortunately didn't help. The switch has helped some
other UI responsiveness though.
*   There is a recurring pigz threads problem occuring in builds. There
is a patch in -next to try and get more debug, the problem has never
occurred with the patch applied. Its unclear if pigz 2.4 has a fix as the
failures only occurred with 2.3.3 (from the host). There are no obvious
differences in the area of the code where the errors occurs between the
versions.
*   There has been a significant change in behaviour in do_package and
handling of pkgdata which should result in better deterministic build and
improve build performance. 
*   We have hopefully now tracked down and resolved the various syslog
restart races and automated testing failures

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) has been submitted to QA.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2484 (last week 2482) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1505 (last week 1509)
*   Patches in the Pending State: 638 (42%) [last week 638 (42%)]

 

Key Status Links for YP:

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

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

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_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!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:   
sjolley.yp...@gmail.com

 

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

Re: [yocto] Poky build errors, help is needed

2019-07-02 Thread Burton, Ross 
On Tue, 2 Jul 2019 at 19:22, Chad Gong  wrote:
> Thank you for the advice. Which folder contains the recipe? Which method is 
> used to calculate the checksum?

Please remember to ensure the list is copied.

$ find . -name opkg-util*bb
./meta/recipes-devtools/opkg-utils/opkg-utils_0.4.1.bb

You're on a different version so the filename won't be the same.  For
the MD5 sum, use md5sum.

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

[yocto] [meta-gplv2][PATCH] gnupg: Enable native build support

2019-07-02 Thread Joshua Watt 
Adds support for building gnupg as a -native recipe.

Signed-off-by: Joshua Watt 
---
 recipes-support/gnupg/gnupg_1.4.7.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-support/gnupg/gnupg_1.4.7.bb 
b/recipes-support/gnupg/gnupg_1.4.7.bb
index 85636ab..a7fbd11 100644
--- a/recipes-support/gnupg/gnupg_1.4.7.bb
+++ b/recipes-support/gnupg/gnupg_1.4.7.bb
@@ -84,6 +84,7 @@ EXTRA_OECONF = "--disable-ldap \
"
 
 # Force gcc's traditional handling of inline to avoid issues with gcc 5
+BUILD_CFLAGS += "-fgnu89-inline"
 CFLAGS += "-fgnu89-inline"
 
 do_install () {
@@ -95,6 +96,8 @@ do_install () {
 
 # split out gpgv from main package
 RDEPENDS_${PN} = "gpgv"
+RDEPENDS_${PN}_class-native = ""
+
 PACKAGES =+ "gpgv"
 FILES_gpgv = "${bindir}/gpgv"
 
@@ -104,3 +107,5 @@ FILES_${PN} = "${bindir}/* ${datadir}/${BPN} 
${libexecdir}/${BPN}/*"
 PACKAGECONFIG ??= ""
 PACKAGECONFIG[curl] = "--with-libcurl=${STAGING_LIBDIR},--without-libcurl,curl"
 PACKAGECONFIG[libusb] = 
"--with-libusb=${STAGING_LIBDIR},--without-libusb,libusb-compat"
+
+BBCLASSEXTEND += "native"
-- 
2.21.0

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

Re: [yocto] Poky build errors, help is needed

2019-07-02 Thread Burton, Ross 
Check that the checksum of the file you grabbed matches the recipe.
There's a MD5 in the recipe that it is comparing against.

Ross

On Tue, 2 Jul 2019 at 16:25, Chad Gong  wrote:
>
> Ross, Gabriele,
>
> I switched to branch 2.7. Still have the same problem as shown below.
>
> ERROR: opkg-utils-0.4.0-r0 do_fetch: Checksum failure fetching 
> http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz
>
>
> When using wget, the files can be downloaded as shown below.
>
> $ wget 
> http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz
> --2019-07-01 20:11:01--  
> http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz
> Resolving git.yoctoproject.org (git.yoctoproject.org)... 140.211.169.56
> Connecting to git.yoctoproject.org 
> (git.yoctoproject.org)|140.211.169.56|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [application/x-gzip]
> Saving to: ‘opkg-utils-0.4.0.tar.gz’
>
> opkg-utils-0.4.0.tar.gz   [ <=>   
>  ]  29.82K  --.-KB/sin 0.005s
>
> 2019-07-01 20:11:02 (5.97 MB/s) - ‘opkg-utils-0.4.0.tar.gz’ saved [30536]
>
>
>
>
>
> Chad Gong
> Electrical Engineer
>
> Trijicon, Inc.
>
>
>  | P.O. Box 930059
> Wixom, Michigan 48393 US
> cg...@trijicon.com |
>
> -Original Message-
> From: Burton, Ross 
> Sent: Tuesday, July 02, 2019 9:00 AM
> To: Chad Gong 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Poky build errors, help is needed
>
> CAUTION: This email originated from outside your organization. Exercise 
> caution when opening attachments or clicking links, especially from unknown 
> senders.
>
> On Tue, 2 Jul 2019 at 13:53, Chad Gong  wrote:
> > WARNING: m4-native-1.4.18-r0 do_fetch: Failed to fetch URL
> > http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz, attempting MIRRORS if
> > available
>
> $ wget http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
> URL transformed to HTTPS due to an HSTS policy
> --2019-07-02 13:59:34--  https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
> Resolving ftp.gnu.org (ftp.gnu.org)... 209.51.188.20, 2001:470:142:3::b 
> Connecting to ftp.gnu.org (ftp.gnu.org)|209.51.188.20|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 2006643 (1.9M) [application/x-gzip] Saving to: ‘m4-1.4.18.tar.gz’
>
> m4-1.4.18.tar.gz
> 100%[===>]
>   1.91M  1.38MB/sin 1.4s
>
> 2019-07-02 13:59:36 (1.38 MB/s) - ‘m4-1.4.18.tar.gz’ saved [2006643/2006643]
>
> Looks like you've got networking problems inside the virtual machine.
> Verify using wget that you can download those files successfully.
>
> Ross
>
>
>
> This electronic message contains information that may be
> confidential, privileged, proprietary, or subject to the export control laws 
> of
> the United States, including the Arms Export Control Act (22 U.S.C. 2571 et
> seq.), the International Traffic in Arms Regulations  (22 C.F.R. Part 120
> et seq.), and/or the Export Administration Regulations (15 C.F.R. Part 730 et
> seq.).  This information is intended for the use of the addressee only, and
> if you are not the intended recipient, any disclosure, copying, distribution,
> printing, or any other use of, the contents of this message is prohibited.
> Any transfer, retransfer, or disclosure of this data to a Foreign Person 
> without
> United States Government authorization is also prohibited.  If you have
> received this message in error, please notify the sender and destroy the
> original message.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Poky build errors, help is needed

2019-07-02 Thread Chad Gong 
Ross, Gabriele,

I switched to branch 2.7. Still have the same problem as shown below.

ERROR: opkg-utils-0.4.0-r0 do_fetch: Checksum failure fetching 
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz


When using wget, the files can be downloaded as shown below.

$ wget 
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz
--2019-07-01 20:11:01--  
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.4.0.tar.gz
Resolving git.yoctoproject.org (git.yoctoproject.org)... 140.211.169.56
Connecting to git.yoctoproject.org (git.yoctoproject.org)|140.211.169.56|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘opkg-utils-0.4.0.tar.gz’

opkg-utils-0.4.0.tar.gz   [ <=> 
   ]  29.82K  --.-KB/sin 0.005s

2019-07-01 20:11:02 (5.97 MB/s) - ‘opkg-utils-0.4.0.tar.gz’ saved [30536]





Chad Gong
Electrical Engineer

Trijicon, Inc.


 | P.O. Box 930059
Wixom, Michigan 48393 US
cg...@trijicon.com |

-Original Message-
From: Burton, Ross 
Sent: Tuesday, July 02, 2019 9:00 AM
To: Chad Gong 
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Poky build errors, help is needed

CAUTION: This email originated from outside your organization. Exercise caution 
when opening attachments or clicking links, especially from unknown senders.

On Tue, 2 Jul 2019 at 13:53, Chad Gong  wrote:
> WARNING: m4-native-1.4.18-r0 do_fetch: Failed to fetch URL
> http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz, attempting MIRRORS if
> available

$ wget http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
URL transformed to HTTPS due to an HSTS policy
--2019-07-02 13:59:34--  https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
Resolving ftp.gnu.org (ftp.gnu.org)... 209.51.188.20, 2001:470:142:3::b 
Connecting to ftp.gnu.org (ftp.gnu.org)|209.51.188.20|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2006643 (1.9M) [application/x-gzip] Saving to: ‘m4-1.4.18.tar.gz’

m4-1.4.18.tar.gz
100%[===>]
  1.91M  1.38MB/sin 1.4s

2019-07-02 13:59:36 (1.38 MB/s) - ‘m4-1.4.18.tar.gz’ saved [2006643/2006643]

Looks like you've got networking problems inside the virtual machine.
Verify using wget that you can download those files successfully.

Ross



This electronic message contains information that may be
confidential, privileged, proprietary, or subject to the export control laws of
the United States, including the Arms Export Control Act (22 U.S.C. 2571 et
seq.), the International Traffic in Arms Regulations  (22 C.F.R. Part 120
et seq.), and/or the Export Administration Regulations (15 C.F.R. Part 730 et
seq.).  This information is intended for the use of the addressee only, and
if you are not the intended recipient, any disclosure, copying, distribution,
printing, or any other use of, the contents of this message is prohibited.
Any transfer, retransfer, or disclosure of this data to a Foreign Person without
United States Government authorization is also prohibited.  If you have
received this message in error, please notify the sender and destroy the
original message.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Anyone built Yocto with Qt5 layer for imx6?

2019-07-02 Thread Onur Eser 
Hello, Yocto Community!
Trying to build Yocto with Qt5 layer for Humming Board 2. But I had almost
a billion of errors and I am so bored. Does anyone had it built? Can you
guys share some steps or configurations with me?
Thanks!
Onur
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

2019-07-02 Thread akuster808 


On 7/1/19 10:26 PM, Jain, Sangeeta wrote:
>
> Hello All,
>
>  
>
> Intel and WR YP QA is planning for QA execution for YP build 2.7.rc1
>
> We are planning to execute following tests for this cycle:
>

I would like to thank Intel and Wind River for doing QA.

>  
>
> OEQA-manual tests for following module:
>
>  
>
> 1. OE-Core
>
> 2. BSP-hw
>
> 3. BSP-Qemu
>
>  
>
> Runtime auto test for following platforms:
>
>  
>
> 1. MinnowTurbot 32-bit
>
> 2. Coffee Lake
>
> 3. NUC 7
>
> 4. NUC 6
>
> 5. Edgerouter
>
> 6. MPC8315e-rdb
>
> 7. Beaglebone
>
>  
>
> ETA for completion is Friday, 5 July.
>

That sounds great.

Thank you
Armin
>
>  
>
>  
>
> Thanks & Regards,
>
> Sangeeta Jain
>
>  
>
>  
>
>  Forwarded Message 
>
> *Subject: *
>
>   
>
> QA notification for completed autobuilder build (yocto-2.7.1.rc1)
>
> *Date: *
>
>   
>
> Mon, 1 Jul 2019 03:08:44 +
>
> *From: *
>
>   
>
> Poky Build User 
> 
>
> *To: *
>
>   
>
> yocto@yoctoproject.org 
>
> *CC: *
>
>   
>
> ota...@ossystems.com.br ,
> yi.z...@windriver.com ,
> apoorv.san...@intel.com ,
> ee.peng.y...@intel.com ,
> aaron.chun.yew.c...@intel.com ,
> chin.huat@intel.com ,
> richard.pur...@linuxfoundation.org
> , akuster...@gmail.com
> , sjolley.yp...@gmail.com
> , sangeeta.j...@intel.com
> 
>
>
>
>
> A build flagged for QA (yocto-2.7.1.rc1) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1
>
>
> Build hash information:
> bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
> meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
> meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
> meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
> oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
> poky: 38d5c8ea98cfa49825c473eba8984c12edf062be
>
>
>
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
>
>

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

Re: [yocto] Poky build errors, help is needed

2019-07-02 Thread Gabriele Zampieri 
Hi Chad,

why are you checking out such an old version? As the tutorial said, try:

git checkout tags/yocto-2.7 -b my-yocto-2.7

Probably some URLs are no longer available.

Gabriele


Il giorno mar 2 lug 2019 alle ore 14:53 Chad Gong  ha
scritto:

> Hi,
>
>
>
> I am new to Yocto project and try to build my first yocto project by
> following instructions on
> https://www.yoctoproject.org/docs/current/brief-yoctoprojectqs/brief-yoctoprojectqs.html.
> I checked out branch yocto-2.5.3, and tried to build targets, such as
> core-image-minimal, meta-toolchain, but always get some fetch errors or
> checksum errors, such as:
>
>
>
> ERROR: libmpc-native-1.1.0-r0 do_fetch: Checksum failure fetching
> https://ftp.gnu.org/gnu/mpc/mpc-1.1.0.tar.gz
>
> WARNING: quilt-native-0.65-r0 do_fetch: Failed to fetch URL
> http://download.savannah.gnu.org/releases/quilt/quilt-0.65.tar.gz,
> attempting MIRRORS if available
>
> WARNING: m4-native-1.4.18-r0 do_fetch: Failed to fetch URL
> http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz, attempting MIRRORS if
> available
>
>
>
> I am running Ubuntu 18.04 virtual box on Windows 7.
>
>
>
> Chad Gong
>
> Electrical Engineer
>
>
>
> Trijicon, Inc.
>
>  | P.O. Box 930059
>
> Wixom, Michigan 48393 US
>
> cg...@trijicon.com |
>
>
>
> --
> This electronic message contains information that may be confidential,
> privileged, proprietary, or subject to the export control laws of the
> United States, including the Arms Export Control Act (22 U.S.C. 2571 et
> seq.), the International Traffic in Arms Regulations  (22 C.F.R. Part 120
> et seq.), and/or the Export Administration Regulations (15 C.F.R. Part 730
> et seq.).  This information is intended for the use of the addressee only,
> and if you are not the intended recipient, any disclosure, copying,
> distribution, printing, or any other use of, the contents of this message
> is prohibited.  Any transfer, retransfer, or disclosure of this data to a
> Foreign Person without United States Government authorization is also
> prohibited.  If you have received this message in error, please notify the
> sender and destroy the original message.
>
> --
> ___
> 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] Poky build errors, help is needed

2019-07-02 Thread Burton, Ross 
On Tue, 2 Jul 2019 at 13:53, Chad Gong  wrote:
> WARNING: m4-native-1.4.18-r0 do_fetch: Failed to fetch URL 
> http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz, attempting MIRRORS if available

$ wget http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
URL transformed to HTTPS due to an HSTS policy
--2019-07-02 13:59:34--  https://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz
Resolving ftp.gnu.org (ftp.gnu.org)... 209.51.188.20, 2001:470:142:3::b
Connecting to ftp.gnu.org (ftp.gnu.org)|209.51.188.20|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2006643 (1.9M) [application/x-gzip]
Saving to: ‘m4-1.4.18.tar.gz’

m4-1.4.18.tar.gz
100%[===>]
  1.91M  1.38MB/sin 1.4s

2019-07-02 13:59:36 (1.38 MB/s) - ‘m4-1.4.18.tar.gz’ saved [2006643/2006643]

Looks like you've got networking problems inside the virtual machine.
Verify using wget that you can download those files successfully.

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

[yocto] Poky build errors, help is needed

2019-07-02 Thread Chad Gong 
Hi,

I am new to Yocto project and try to build my first yocto project by following 
instructions on 
https://www.yoctoproject.org/docs/current/brief-yoctoprojectqs/brief-yoctoprojectqs.html.
 I checked out branch yocto-2.5.3, and tried to build targets, such as 
core-image-minimal, meta-toolchain, but always get some fetch errors or 
checksum errors, such as:

ERROR: libmpc-native-1.1.0-r0 do_fetch: Checksum failure fetching 
https://ftp.gnu.org/gnu/mpc/mpc-1.1.0.tar.gz
WARNING: quilt-native-0.65-r0 do_fetch: Failed to fetch URL 
http://download.savannah.gnu.org/releases/quilt/quilt-0.65.tar.gz, attempting 
MIRRORS if available
WARNING: m4-native-1.4.18-r0 do_fetch: Failed to fetch URL 
http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.gz, attempting MIRRORS if available

I am running Ubuntu 18.04 virtual box on Windows 7.



Chad Gong

Electrical Engineer



Trijicon, Inc.

 | P.O. Box 930059

Wixom, Michigan 48393 US

cg...@trijicon.com |




This electronic message contains information that may be confidential, 
privileged, proprietary, or subject to the export control laws of the United 
States, including the Arms Export Control Act (22 U.S.C. 2571 et seq.), the 
International Traffic in Arms Regulations  (22 C.F.R. Part 120 et seq.), and/or 
the Export Administration Regulations (15 C.F.R. Part 730 et seq.).  This 
information is intended for the use of the addressee only, and if you are not 
the intended recipient, any disclosure, copying, distribution, printing, or any 
other use of, the contents of this message is prohibited.  Any transfer, 
retransfer, or disclosure of this data to a Foreign Person without United 
States Government authorization is also prohibited.  If you have received this 
message in error, please notify the sender and destroy the original message.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Recursion error in do_package task, building libgcc_8.3

2019-07-02 Thread Ekaterini Voulgari 

Hello,
I'm building a custom image (based on poky-tiny distro with newlib) and 
I get a symlink recursion error at strip_files. Ι've found 
this:https://lists.yoctoproject.org/pipermail/yocto/2019-June/045838.html 
of some relevance. I tried with:


   INHIBIT_SYSROOT_STRIP = "1"
   INHIBIT_PACKAGE_STRIP = "1"
   INSANE_SKIP_${PN} = "ldflags"
   INSANE_SKIP_${PN} = "already-stripped"

in local.conf in which case I only get the second error(do_package).

What causes that recursion and where do I start looking to fix it?


ERROR: libgcc-8.3.0-r0 do_populate_sysroot: Error executing a python 
function in exec_python_func() autogenerated:


The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:sysroot_strip(d)
 0003:
File: '/home/***/poky/meta/classes/staging.bbclass', lineno: 83, 
function: sysroot_strip
 0079:    qa_already_stripped = 'already-stripped' in 
(d.getVar('INSANE_SKIP_' + pn) or "").split()

 0080:    strip_cmd = d.getVar("STRIP")
 0081:
 0082:    oe.package.strip_execs(pn, dstdir, strip_cmd, libdir, 
base_libdir, d,

 *** 0083: qa_already_stripped=qa_already_stripped)
 0084:}
 0085:
 0086:do_populate_sysroot[dirs] = "${SYSROOT_DESTDIR}"
 0087:do_populate_sysroot[umask] = "022"
File: '/home/***/poky/meta/lib/oe/package.py', lineno: 123, function: 
strip_execs

 0119:    for f in files:
 0120:    file = os.path.join(root, f)
 0121:
 0122:    try:
 *** 0123:    ltarget = oe.path.realpath(file, dstdir, False)
 0124:    s = os.lstat(ltarget)
 0125:    except OSError as e:
 0126:    (err, strerror) = e.args
 0127:    if err != errno.ENOENT:
File: '/home/***/poky/meta/lib/oe/path.py', lineno: 235, function: realpath
 0231:    # be printed a backtrace with 100s of OSError 
exceptions

 0232:    # else
 0233:    raise OSError(errno.ELOOP,
 0234:  "too much recursions while 
resolving '%s'; loop in '%s'" %

 *** 0235:  (file, e.strerror))
 0236:
 0237:    raise
 0238:
 0239:    return file
Exception: OSError: [Errno 40] too much recursions while resolving 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/sysroot-destdir/usr/lib/arm-poky-eabi/arm-poky-eabi'; 
loop in 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/sysroot-destdir/usr/lib/arm-poky-eabi/arm-poky-eabi'


ERROR: libgcc-8.3.0-r0 do_populate_sysroot: [Errno 40] too much 
recursions while resolving 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/sysroot-destdir/usr/lib/arm-poky-eabi/arm-poky-eabi'; 
loop in 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/sysroot-destdir/usr/lib/arm-poky-eabi/arm-poky-eabi'

ERROR: libgcc-8.3.0-r0 do_populate_sysroot: Function failed: sysroot_strip
ERROR: Logfile of failure stored in: 
/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/temp/log.do_populate_sysroot.28604
ERROR: Task 
(/home/***/poky/meta/recipes-devtools/gcc/libgcc_8.3.bb:do_populate_sysroot) 
failed with exit code '1'
ERROR: libgcc-8.3.0-r0 do_package: Error executing a python function in 
exec_python_func() autogenerated:


The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:split_and_strip_files(d)
 0003:
File: '/home/***/poky/meta/classes/package.bbclass', lineno: 974, 
function: split_and_strip_files

 0970:    if file in skipfiles:
 0971:    continue
 0972:
 0973:    try:
 *** 0974:    ltarget = cpath.realpath(file, dvar, False)
 0975:    s = cpath.lstat(ltarget)
 0976:    except OSError as e:
 0977:    (err, strerror) = e.args
 0978:    if err != errno.ENOENT:
File: '/home/***/poky/meta/lib/oe/cachedpath.py', lineno: 229, function: 
realpath
 0225:    # be printed a backtrace with 100s of OSError 
exceptions

 0226:    # else
 0227:    raise OSError(errno.ELOOP,
 0228:  "too much recursions while 
resolving '%s'; loop in '%s'" %

 *** 0229:  (file, e.strerror))
 0230:
 0231:    raise
 0232:
 0233:    return file
Exception: OSError: [Errno 40] too much recursions while resolving 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/package/usr/lib/arm-poky-eabi/arm-poky-eabi'; 
loop in 
'/home/***/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-eabi/libgcc/8.3.0-r0/package/usr/lib/arm-poky-eabi/arm-poky-eabi'

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

2019-07-02 Thread Burton, Ross 
On Tue, 2 Jul 2019 at 08:05, Zoran Stojsavljevic
 wrote:
> >> Runtime auto test for following platforms:
> >> 1. MinnowTurbot 32-bit (Appolo Lake?)
> >> 2. Coffee Lake (14nm 4th tock in the row)
> >> 3. NUC 7
> >> 4. NUC 6
> >> 5. Edgerouter
> >> 6. MPC8315e-rdb
> >> 7. BeagleboneHm...
>
> At least first four from the list are IA (INTEL Architecture)... Maybe
> even fifth (Edgerouter). Nummer Sieben (number 7 - Beagle Bone) should
> move at least to numero due (number 2). IMHO. ;-)

Some points:
1) Consider that a bullet list, not an ordered list
2) Are you surprised that Intel QA is testing on Intel hardware?
3) Edgerouter is MIPS:

$ grep tune meta-yocto-bsp/conf/machine/edgerouter.conf
require conf/machine/include/tune-mips64.inc

So that's a selection of IA, MIPS, PPC, ARM.  At least one of all the
primary supported architectures.

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

Re: [yocto] Allow choose of U-Boot config for machine

2019-07-02 Thread JH 
Thank you very much Gabriele, appreciate it.

On 7/2/19, Gabriele Zampieri  wrote:
> Since UBOOT_CONFIG is a standard property, I suggest you to read the
> following links:
>
>-
>
> https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-UBOOT_CONFIG
>-
>
> https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-UBOOT_MACHINE
>
> Please not that the links I provided refers to the latest documentation,
> you should check the docs for your YP version.
>
> About testing, I have no idea about how to test uboot without the target
> board. If you are planning to use a commercial solution which is supported
> by Yocto, you should be safe enough for now.
>
> Gabriele
>
> Il giorno mar 2 lug 2019 alle ore 09:40 JH  ha
> scritto:
>
>> Thanks Gabriele, you are right, it did not work in command line but it
>> did not complain after UBOOT_CONFIG = "nand" to local.conf, how can I
>> am sure it is built to boot from nand? I don't have a board to try
>> yet.
>>
>> Thank you very much.
>>
>> Kind regards,
>>
>> - jh
>>
>>
>> On 7/2/19, Gabriele Zampieri  wrote:
>> > Hi,
>> >
>> > you must use double quotes around nand, so:
>> > UBOOT_CONFIG = "nand"
>> >
>> > However I cannot guarantee this line will be the solution, I usually
>> > use
>> a
>> > customized uboot.
>> >
>> > Gabriele
>> >
>> > Il giorno mar 2 lug 2019 alle ore 04:07 JH  ha
>> > scritto:
>> >
>> >> Hi,
>> >>
>> >> The imx6ullevk.conf defined sdcard for booting on imx6 EVK:
>> >>
>> >> imx6ullevk.conf
>> >>
>> >> UBOOT_CONFIG ??= "sd"
>> >> UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
>> >> UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"
>> >>
>> >> I need to change it for a customized board referenced from imx6 EVK
>> >> but booting from NAND, there are some blogs said it can be done to add
>> >> UBOOT_CONFIG=nand either in local.conf or command line. I tried it did
>> >> not work:
>> >>
>> >> ERROR: Unable to start bitbake server (None)
>> >> --- Starting bitbake server pid 2673 at 2019-07-02 11:54:24.011086 ---
>> >> ERROR: local.conf:34: unparsed line: 'UBOOT_CONFIG=nand'
>> >>
>> >> What should be a proper process to overwrite imx6ullevk.conf
>> >> UBOOT_CONFIG from sdcard to nand?
>> >>
>> >> Thank you.
>> >>
>> >> Kind regards,
>> >>
>> >> - JH
>> >> --
>> >> ___
>> >> 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] Getting a package PV from another

2019-07-02 Thread Gabriele Zampieri 
Hi Mike,

thank you for your reply. The meta-layer that we use are locked (they won't
be changed once in production, so the git hash won't tell much about). I
need that information for tracking/distribution purposes, since I already
have a way to get it at runtime.

Gabriele

Il giorno lun 1 lug 2019 alle ore 15:23 Mike Looijmans <
mike.looijm...@topic.nl> ha scritto:

> The version of your OE layer is all the version that you'll ever
> (technically)
> need. That version (usually a git hash) dictates all other versions.
>
> When asked for version numbers of included packages, I always just dump
> the
> manifest file into their lap.
>
> You can also ask and report the version numbers at runtime (e.g. using
> opkg or
> dpkg). That also prevents lying to your users :)
>
> On 01-07-19 11:28, Gabriele Zampieri wrote:
> > Up, with more details:
> >
> > I have a top recipe that depends on *my-image:do_build*. I'd like to
> retrieve
> > the PV of a couple of packages (from that top recipe) that are used to
> mark
> > our custom software. Any suggestions?
> >
> > Gabriele
> >
> > Il giorno ven 28 giu 2019 alle ore 11:25 Gabriele Zampieri
> > mailto:gabbla.mal...@gmail.com>> ha scritto:
> >
> > Hi all,
> >
> > is there a way to get a specific package version from another?
> >
> > Best regards,
> > Gabriele
> >
> >
>
> --
> ___
> 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] Allow choose of U-Boot config for machine

2019-07-02 Thread Gabriele Zampieri 
Since UBOOT_CONFIG is a standard property, I suggest you to read the
following links:

   -
   
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-UBOOT_CONFIG
   -
   
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-UBOOT_MACHINE

Please not that the links I provided refers to the latest documentation,
you should check the docs for your YP version.

About testing, I have no idea about how to test uboot without the target
board. If you are planning to use a commercial solution which is supported
by Yocto, you should be safe enough for now.

Gabriele

Il giorno mar 2 lug 2019 alle ore 09:40 JH  ha
scritto:

> Thanks Gabriele, you are right, it did not work in command line but it
> did not complain after UBOOT_CONFIG = "nand" to local.conf, how can I
> am sure it is built to boot from nand? I don't have a board to try
> yet.
>
> Thank you very much.
>
> Kind regards,
>
> - jh
>
>
> On 7/2/19, Gabriele Zampieri  wrote:
> > Hi,
> >
> > you must use double quotes around nand, so:
> > UBOOT_CONFIG = "nand"
> >
> > However I cannot guarantee this line will be the solution, I usually use
> a
> > customized uboot.
> >
> > Gabriele
> >
> > Il giorno mar 2 lug 2019 alle ore 04:07 JH  ha
> > scritto:
> >
> >> Hi,
> >>
> >> The imx6ullevk.conf defined sdcard for booting on imx6 EVK:
> >>
> >> imx6ullevk.conf
> >>
> >> UBOOT_CONFIG ??= "sd"
> >> UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
> >> UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"
> >>
> >> I need to change it for a customized board referenced from imx6 EVK
> >> but booting from NAND, there are some blogs said it can be done to add
> >> UBOOT_CONFIG=nand either in local.conf or command line. I tried it did
> >> not work:
> >>
> >> ERROR: Unable to start bitbake server (None)
> >> --- Starting bitbake server pid 2673 at 2019-07-02 11:54:24.011086 ---
> >> ERROR: local.conf:34: unparsed line: 'UBOOT_CONFIG=nand'
> >>
> >> What should be a proper process to overwrite imx6ullevk.conf
> >> UBOOT_CONFIG from sdcard to nand?
> >>
> >> Thank you.
> >>
> >> Kind regards,
> >>
> >> - JH
> >> --
> >> ___
> >> 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] Allow choose of U-Boot config for machine

2019-07-02 Thread JH 
Thanks Gabriele, you are right, it did not work in command line but it
did not complain after UBOOT_CONFIG = "nand" to local.conf, how can I
am sure it is built to boot from nand? I don't have a board to try
yet.

Thank you very much.

Kind regards,

- jh


On 7/2/19, Gabriele Zampieri  wrote:
> Hi,
>
> you must use double quotes around nand, so:
> UBOOT_CONFIG = "nand"
>
> However I cannot guarantee this line will be the solution, I usually use a
> customized uboot.
>
> Gabriele
>
> Il giorno mar 2 lug 2019 alle ore 04:07 JH  ha
> scritto:
>
>> Hi,
>>
>> The imx6ullevk.conf defined sdcard for booting on imx6 EVK:
>>
>> imx6ullevk.conf
>>
>> UBOOT_CONFIG ??= "sd"
>> UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
>> UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"
>>
>> I need to change it for a customized board referenced from imx6 EVK
>> but booting from NAND, there are some blogs said it can be done to add
>> UBOOT_CONFIG=nand either in local.conf or command line. I tried it did
>> not work:
>>
>> ERROR: Unable to start bitbake server (None)
>> --- Starting bitbake server pid 2673 at 2019-07-02 11:54:24.011086 ---
>> ERROR: local.conf:34: unparsed line: 'UBOOT_CONFIG=nand'
>>
>> What should be a proper process to overwrite imx6ullevk.conf
>> UBOOT_CONFIG from sdcard to nand?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - JH
>> --
>> ___
>> 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] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

2019-07-02 Thread Zoran Stojsavljevic 
>> Runtime auto test for following platforms:
>> 1. MinnowTurbot 32-bit (Appolo Lake?)
>> 2. Coffee Lake (14nm 4th tock in the row)
>> 3. NUC 7
>> 4. NUC 6
>> 5. Edgerouter
>> 6. MPC8315e-rdb
>> 7. BeagleboneHm...

At least first four from the list are IA (INTEL Architecture)... Maybe
even fifth (Edgerouter). Nummer Sieben (number 7 - Beagle Bone) should
move at least to numero due (number 2). IMHO. ;-)

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