[yocto] Hello from Me, Richard
Just wanted to introduce myself. I'm working at a startup in the UK and my job is to manage and create the embedded platform that the product will run on. ttfn, Richard. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Getting the version of Yocto that is being used.
I've inherited a Yocto project that I know to be an old version. So one of my tasks is to update to the latest version. Before I do this I would like to know what version I have. The only information I can find is the bitbake version, BB_VERSION= "1.32.0". Many thanks, Richard. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
If your project also includes meta-poky then poky.conf will contain a DISTRO_VERSION assignment. However, https://wiki.yoctoproject.org/wiki/Releases indicates that bitbake 1.32 was part of 2.2/morty. Ross On 12 April 2018 at 10:44, Richard Collins wrote: > I've inherited a Yocto project that I know to be an old version. So one of > my tasks is to update to the latest version. Before I do this I would like > to know what version I have. The only information I can find is the bitbake > version, BB_VERSION= "1.32.0". > > Many thanks, > Richard. > > > -- > ___ > 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 the version of Yocto that is being used.
On 04/12/2018 12:44 PM, Richard Collins wrote: I've inherited a Yocto project that I know to be an old version. So one of my tasks is to update to the latest version. Before I do this I would like to know what version I have. The only information I can find is the bitbake version, BB_VERSION = "1.32.0". When you run bitbake, it should also print the values of DISTRO and DISTRO_VERSION. Those should give a clue where you are at. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
I get the following for DISTRO. DISTRO= "yogurt" DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" Can't find any reference to yogurt so I assume this is something the supplier of our SOM's has done. Looking on their Wiki it seems to be based on 2.1.2 (Krogoth) Thanks for the help. :) On 12 April 2018 at 11:21, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 04/12/2018 12:44 PM, Richard Collins wrote: > >> I've inherited a Yocto project that I know to be an old version. So one >> of my tasks is to update to the latest version. Before I do this I would >> like to know what version I have. The only information I can find is the >> bitbake version, BB_VERSION= "1.32.0". >> > > When you run bitbake, it should also print the values of DISTRO and > DISTRO_VERSION. Those should give a clue where you are at. > > Alex > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
I think the message here is that we need to embed the oe-core version in the metadata somewhere... On 12 April 2018 at 13:11, Richard Collins wrote: > I get the following for DISTRO. > > DISTRO= "yogurt" > DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" > > Can't find any reference to yogurt so I assume this is something the > supplier of our SOM's has done. Looking on their Wiki it seems to be based > on 2.1.2 (Krogoth) > > > Thanks for the help. :) > > On 12 April 2018 at 11:21, Alexander Kanavin > wrote: >> >> On 04/12/2018 12:44 PM, Richard Collins wrote: >>> >>> I've inherited a Yocto project that I know to be an old version. So one >>> of my tasks is to update to the latest version. Before I do this I would >>> like to know what version I have. The only information I can find is the >>> bitbake version, BB_VERSION= "1.32.0". >> >> >> When you run bitbake, it should also print the values of DISTRO and >> DISTRO_VERSION. Those should give a clue where you are at. >> >> Alex > > > > -- > ___ > 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 the version of Yocto that is being used.
Cannot LAYERSERIES_CORENAMES added in rocko be used for that? On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote: > I think the message here is that we need to embed the oe-core version > in the metadata somewhere... > > On 12 April 2018 at 13:11, Richard Collins > wrote: > > I get the following for DISTRO. > > > > DISTRO= "yogurt" > > DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" > > > > Can't find any reference to yogurt so I assume this is something the > > supplier of our SOM's has done. Looking on their Wiki it seems to be > based > > on 2.1.2 (Krogoth) > > > > > > Thanks for the help. :) > > > > On 12 April 2018 at 11:21, Alexander Kanavin > > wrote: > >> > >> On 04/12/2018 12:44 PM, Richard Collins wrote: > >>> > >>> I've inherited a Yocto project that I know to be an old version. So one > >>> of my tasks is to update to the latest version. Before I do this I > would > >>> like to know what version I have. The only information I can find is > the > >>> bitbake version, BB_VERSION= "1.32.0". > >> > >> > >> When you run bitbake, it should also print the values of DISTRO and > >> DISTRO_VERSION. Those should give a clue where you are at. > >> > >> Alex > > > > > > > > -- > > ___ > > 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
That is an excellent suggestion, yes. Ross On 12 April 2018 at 13:54, Martin Jansa wrote: > Cannot LAYERSERIES_CORENAMES added in rocko be used for that? > > On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote: >> >> I think the message here is that we need to embed the oe-core version >> in the metadata somewhere... >> >> On 12 April 2018 at 13:11, Richard Collins >> wrote: >> > I get the following for DISTRO. >> > >> > DISTRO= "yogurt" >> > DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" >> > >> > Can't find any reference to yogurt so I assume this is something the >> > supplier of our SOM's has done. Looking on their Wiki it seems to be >> > based >> > on 2.1.2 (Krogoth) >> > >> > >> > Thanks for the help. :) >> > >> > On 12 April 2018 at 11:21, Alexander Kanavin >> > wrote: >> >> >> >> On 04/12/2018 12:44 PM, Richard Collins wrote: >> >>> >> >>> I've inherited a Yocto project that I know to be an old version. So >> >>> one >> >>> of my tasks is to update to the latest version. Before I do this I >> >>> would >> >>> like to know what version I have. The only information I can find is >> >>> the >> >>> bitbake version, BB_VERSION= "1.32.0". >> >> >> >> >> >> When you run bitbake, it should also print the values of DISTRO and >> >> DISTRO_VERSION. Those should give a clue where you are at. >> >> >> >> Alex >> > >> > >> > >> > -- >> > ___ >> > 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Boot Question
I actually resolved my first issue today - the install on SSD from USB thumb drive's .hddimg seemed correct. There're probably user's prompts on the boot console that I didn't pay attention to at first (I used COM1, which wasn't the boot console). I'd tried removing thumb drive, and changed boot order to use the SSD, and it worked. I'd even made some progress on the network-boot client side. The key steps for me were to switch to UEFI Standard instead of Legacy mode. Then enabled PXE option ROM Launch. This would create a few network devices (with IPv4 and IPv6 options) to support PXE. I now focus on the server side. Hopefully, I will have some good news to share shortly. My eval board is based on Intel's Broadwell DE (Camelback Mountain BSP) from Intel. Machine type is intel-corei7-64. Hope this help. Raymond From: Mohammad, Jamal M Sent: Tuesday, April 10, 2018 9:48 PM To: Raymond Yeung; yocto@yoctoproject.org Subject: RE: Yocto Boot Question I also faced a similar issue while installing on Intel machine, switching to other machine I was able to install and boot successfully.. I have not tried network boot option.. Which is the board you are using and what is the machine type? Regards, Jamal From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Raymond Yeung Sent: Tuesday, April 10, 2018 10:53 PM To: yocto@yoctoproject.org Subject: [yocto] Yocto Boot Question Hi, I've successfully booted a BSP using USB thumb drive (.hddimg type). I've two follow-up questions - 1. The BIOS offers "Serial Install" which seems to copy the USB boot image over to SSD. Would SSD be using the same .hddimg type? Right now, after the above install, when I switch boot order to try both SSD (0 and 1), booting doesn't seem to work. 2. When using network boot option, what image type should I use? It would be great if details have already been documented somewhere. Thanks, Raymond -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
On 04/12/2018 03:11 PM, Richard Collins wrote: I get the following for DISTRO. DISTRO = "yogurt" DISTRO_VERSION = "BSP-Yocto-RK3288-PD17.1.1" Can't find any reference to yogurt so I assume this is something the supplier of our SOM's has done. Looking on their Wiki it seems to be based on 2.1.2 (Krogoth) This is probably coming from meta-yogurt layer provided by a company called Phytec. Looking at their git repository, they have branches for all Yocto releases, so you could probably start by looking at that. Generally, Phytec should be your support channel :) Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 1/3] sssd: only include when pam in DISTRO_FEATURES
Signed-off-by: Armin Kuster
---
recipes-security/sssd/sssd_1.16.0.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/recipes-security/sssd/sssd_1.16.0.bb
b/recipes-security/sssd/sssd_1.16.0.bb
index e41a38e..ff5b618 100644
--- a/recipes-security/sssd/sssd_1.16.0.bb
+++ b/recipes-security/sssd/sssd_1.16.0.bb
@@ -14,7 +14,9 @@ SRC_URI =
"https://releases.pagure.org/SSSD/${BPN}/${BP}.tar.gz\
SRC_URI[md5sum] = "f721ace2ebfa6744cfea55e3ecd2d82f"
SRC_URI[sha256sum] =
"c581a6e5365cef87fca419c0c9563cf15eadbb682863d648d85ffcded7a3940f"
-inherit autotools pkgconfig gettext update-rc.d python-dir
+inherit autotools pkgconfig gettext update-rc.d python-dir
distro_features_check
+
+REQUIRED_DISTRO_FEATURES = "pam"
CACHED_CONFIGUREVARS = "ac_cv_member_struct_ldap_conncb_lc_arg=no \
ac_cv_path_NSUPDATE=${bindir} \
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 2/3] clamav: update LLVM version to match core
Signed-off-by: Armin Kuster
---
recipes-security/clamav/clamav_0.99.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/clamav/clamav_0.99.3.bb
b/recipes-security/clamav/clamav_0.99.3.bb
index dc26277..043fa21 100644
--- a/recipes-security/clamav/clamav_0.99.3.bb
+++ b/recipes-security/clamav/clamav_0.99.3.bb
@@ -35,7 +35,7 @@ GID = "clamav"
# as defined below
CLAMAV_LLVM ?= "oellvm"
-CLAMAV_LLVM_RELEASE ?= "5.0"
+CLAMAV_LLVM_RELEASE ?= "6.0"
PACKAGECONFIG ?= "ncurses openssl bz2 zlib ${CLAMAV_LLVM}"
PACKAGECONFIG += " ${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6", "",
d)}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 3/3] meta-security: remove depened on other security layers
Signed-off-by: Armin Kuster
---
conf/layer.conf | 3 ---
1 file changed, 3 deletions(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 04605a1..efc426e 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -12,6 +12,3 @@ BBFILE_PRIORITY_security = "6"
LAYERSERIES_COMPAT_security = "sumo"
LAYERDEPENDS_security = "core openembedded-layer perl-layer networking-layer
meta-python"
-LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "tpm",
"tpm-layer", "",d)}"
-LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "tpm2",
"tpm-layer", "",d)}"
-LAYERDEPENDS_security += "${@bb.utils.contains("MACHINE_FEATURES", "vtpm",
"tpm-layer meta-filesystems", "",d)}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to update OpenCV to 3.3 in Krogoth branch of Yocto in i.MX6
Hello Nishina, Any progress on the issue? Thank you, Zoran ___ On Tue, Apr 10, 2018 at 8:47 AM, Nishina A. Pervin wrote: > Hi, > > > > How can we update OpenCV to 3.3 from 3.1 in Krogoth branch of Yocto for > i.MX6 board > > > > Regards, > > Nishina > > > > Confidentiality Statement / Disclaimer : This message and any attachments is > intended for the sole use of the intended recipient. It may contain > confidential information. Any unauthorized use, dissemination or > modification is strictly prohibited. If you are not the intended recipient, > please notify the sender immediately then delete it from all your systems, > and do not copy, use or print. Internet communications are not secure and it > is the responsibility of the recipient to make sure that it is > virus/malicious code exempt. > > The company/sender cannot be responsible for any unauthorized alterations or > modifications made to the contents. If you require any form of confirmation > of the contents, please contact the company/sender. The company/sender is > not liable for any errors or omissions in the content of this 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] out of tree module dependencies
On 4/10/18 8:57 AM, RUSSELL PETERSON wrote: > I have been debugging this issue and could use some advice. > > The basic issue I see is that do_make_scripts executes and fails. I have > seen different fails but in the end it all comes back to something being > required in recipe-sysroot or recipe-sysroot-native and it's not there. > For instance gcc-cross-aarch64 is missing from recipe-sysroot-native. > > Yocto build dependencies is a rather advanced topic and I certainly > don't feel I understand exactly what the issue is... but here is my guess. > > 1. I changed my linux kernel recipe. > 2. Because of #1, the cross compiler decided to rebuild. Generally, this > isn't an issue. In fact the old cross compiler should *still* be in > recipe-sysroot-native. > 3. Once the kernel build artifacts is done... my module recipes fire. > The first thing they want to do is run do_cve_check. > 4. This is the part that causes the problem... do_cve_check DELETES > gcc-cross-aarch64 from the sysroot! This is because it cannot find > gcc-cross-aarch64.complete... which points to a manifest file. I think > this manifest file is created by the > gcc-cross-aarch64.do_populate_sysroot. Problem is, cve_check does not > depend on that? > This seems a bug to me. Please open a ticket in yocto project bugzilla -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Getting the version of Yocto that is being used.
On Thu, Apr 12, 2018 at 01:11:17PM +0100, Richard Collins wrote: > I get the following for DISTRO. > > DISTRO= "yogurt" > DISTRO_VERSION= "BSP-Yocto-RK3288-PD17.1.1" > For further reference by anyone who is reading this in the archive: the supplier is Phytec, and the distro layer is here: https://git.phytec.de/meta-yogurt/ Greetz -- ——— 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
[yocto] [ANNOUNCEMENT] Milestone 3 for Yocto Project 2.5 (yocto-2.5_M3) now available
We are pleased to announce the third milestone release for Yocto Project 2.5 (yocto-2.5_M3) is available for download now. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.5_M3/ poky f49ee61422c867516db252054e993df29f775136 bitbake 39d6a30a28f66c599e18beddbd847f40dcff623c eclipse-poky-neon a5dbc01b96be55c4ec2f774af9996a8086e402ab eclipse-poky-oxygen fbb91e5c5ad06470cd50ce1daa407a5f7d13c6ca meta-qt3 f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-qt4 f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d meta-gplv2 c591f97432047a2add48ff0ec9c20babba2915c6 meta-intel 11c2d33606669ab77467c040b5f45a6e3e188dd8 meta-mingw a07fe304228b7f41b5558de7d8f39fd5e8a430d2 Test report: https://wiki.yoctoproject.org/wiki/WW15_-_2018-04-09-_Full_Test_Cycle_-_2.5_M3_rc1 Thank you. Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw][PATCH] diffutils_3.6: build for mingw
Build of diffutils was requested/broken for mingw because of the commit
"diffutils: allow native & nativesdk builds"
This patch implements neccessary steps needed to build diffutils executables:
cmp.exe
diff.exe
diff3.exe
sdiff.exe
[YOCTO #12662]
Signed-off-by: Juro Bystricky
---
.../diffutils/diffutils/sdiff-no-kill.patch| 18 ++
recipes-extended/diffutils/diffutils_3.6.bbappend | 18 ++
2 files changed, 36 insertions(+)
create mode 100644 recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
create mode 100644 recipes-extended/diffutils/diffutils_3.6.bbappend
diff --git a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
new file mode 100644
index 000..70e7caf
--- /dev/null
+++ b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
@@ -0,0 +1,18 @@
+"kill" is not supported by mingw, so compile conditionally,
+(same condition as another instance of "kill" in the source code).
+
+Upstream-Status: Pending
+Signed-off-by: Juro Bystricky
+
+--- a/src/sdiff.c
b/src/sdiff.c
+@@ -805,7 +805,9 @@
+
+ /* Yield an exit status indicating that a signal was received. */
+ untrapsig (s);
++#if HAVE_WORKING_FORK
+ kill (getpid (), s);
++#endif
+
+ /* That didn't work, so exit with error status. */
+ exit (EXIT_TROUBLE);
diff --git a/recipes-extended/diffutils/diffutils_3.6.bbappend
b/recipes-extended/diffutils/diffutils_3.6.bbappend
new file mode 100644
index 000..f301349
--- /dev/null
+++ b/recipes-extended/diffutils/diffutils_3.6.bbappend
@@ -0,0 +1,18 @@
+
+FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/${BPN}:"
+
+SRC_URI_remove_mingw32 =
"file://0001-explicitly-disable-replacing-getopt.patch"
+SRC_URI_append_mingw32 = " file://sdiff-no-kill.patch"
+
+CACHED_CONFIGUREVARS_append_mingw32 = " ac_cv_header_getopt_h=yes "
+
+# Add some definitions for POSIX signals..
+CFLAGS_append_mingw32 = " -DSIGALRM=14 -DSIGHUP=1 -DSIGQUIT=3 -DSIGPIPE=13
-DSIGTSTP=18 -DSIGSTOP=17 "
+
+do_configure_prepend_mingw32 () {
+# Remove building of "man"
+sed -i -e 's:^SUBDIRS = lib src tests doc man po gnulib-test:SUBDIRS = lib
src tests doc po gnulib-test:g' ${S}/Makefile.am
+}
+
+
+
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw
The commit "qemu: Bump to version 2.11.0" in oe-core broke the build of qemu for mingw, due to using "socketpair", which is not supported by mingw. "socketpair" is used in a local patch, not in the qemu upstream code. The original local patch had conditional code to exclude "socketpair" for _WIN32, but the modified patch for qemu 2.11.0 removed this. The fix is to simply remove the offending patch. Signed-off-by: Juro Bystricky --- recipes-devtools/qemu/qemu_2.11.%.bbappend | 4 1 file changed, 4 insertions(+) create mode 100644 recipes-devtools/qemu/qemu_2.11.%.bbappend diff --git a/recipes-devtools/qemu/qemu_2.11.%.bbappend b/recipes-devtools/qemu/qemu_2.11.%.bbappend new file mode 100644 index 000..764b500 --- /dev/null +++ b/recipes-devtools/qemu/qemu_2.11.%.bbappend @@ -0,0 +1,4 @@ + + +SRC_URI_remove_mingw32 = "file://chardev-connect-socket-to-a-spawned-command.patch" + -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw][PATCH] nativesdk-packagegroup-sdk-host: add qemu
Now that we can build qemu for mingw, include it in SDK.
Signed-off-by: Juro Bystricky
---
recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend | 1 +
1 file changed, 1 insertion(+)
diff --git
a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
index 9629354..ad69b13 100644
--- a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
+++ b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
@@ -1,4 +1,5 @@
RDEPENDS_${PN}_mingw32 = "\
nativesdk-pkgconfig \
nativesdk-libtool \
+nativesdk-qemu \
"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Which recipe produce that file?
Hi all. My name's Mauro and I write from Parma, Italy. I'm in trouble because recently I get a collision error. It seems that more than one recipes try to install the same file in the same path in populate_sdk task This is an example -- ERROR: xcb-util-0.4.0-r0 do_populate_sysroot: The recipe xcb-util is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/libxcb-util.la /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/libxcb-util.so /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/libxcb-util.so.1.0.0 /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/libxcb-util.a /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/libxcb-util.so.1 /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/pkgconfig/xcb-event.pc /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/pkgconfig/xcb-util.pc /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/pkgconfig/xcb-aux.pc /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/lib/pkgconfig/xcb-atom.pc /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/include/xcb/xcb_event.h /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/include/xcb/xcb_util.h /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/include/xcb/xcb_aux.h /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/usr/include/xcb/xcb_atom.h /media/mauro/Sviluppo/CatellaniGroup/ibr115/bsp/clini5-build/tmp/sysroots/imx6dlsabresd/sysroot-providers/xcb-util -- I'm working with a Jethro distro How can I solve this problem? Best regards, MZ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
