[yocto] How to install command locale & localedef for my image
Hi all I want to install command locale & localedef for my image, so I tried the following: IMAGE_INSTALL_append = " glibc-locale" But it didn't work, so how can I install the above command? //xiaoyang -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] swabber: remove from documentation
Hi Scott, On Fri, Jul 22, 2016 at 08:14:24AM -0700, Scott Rifenbark wrote: >Hi, > >>Is it safe to apply this patch to the docs? In the past, I have applied >>patches too soon to the docs. Let me know. Since swabber support in oe-core is a dead parrot now, this patch is safe to apply to the docs :) >Thanks, >Scott >> >>On Fri, Jul 22, 2016 at 4:28 AM, Maxin B. John wrote: >> >> Remove documentation as swabber was removed from >> oe-core with this commit: >> commit a7ddbea345c90646e6b9ddb89f768865caffdf07 >> Author: Richard Purdie >> Date: Mon Jun 6 12:08:56 2016 +010 Best Regards, Maxin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, June 7, 2016 8:00 AM US Pacific Time
On 08/02/2016 11:23 AM, Jolley, Stephen K wrote: > Attendees: Saul, David Wolfe, Joshua, Belen, Ross, Mark, Bill > > Poky - LTS/LTM Branch > - Community Driven > - 2 Years > - Companies continue to push on older branches that they are > interested in. > - Most patches would be in Oe-Core meta-data This kind of jumped out at me. Can anyone explain why the Yocto Project needs an LTS version of the reference distribution? Philip > > * Team Sharing - 10 min > RP has branch with multi-config in parallel > - fixes various other tools > - Distributed builds in 2.2 is unlikely due to resource constraits > > Thanks, > > Sau! > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] problem with package architecture
Hej I am using the actual Yocto version. A Yocto Linux I is build based on the meta-atmel layer. The system seems to be "armel" but the packages are for "armhf". When running bitbake it shows: ## Build Configuration: BB_VERSION= "1.30.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "sama5d3xek" DISTRO= "poky-atmel" DISTRO_VERSION= "2.1.1" TUNE_FEATURES = "arm armv7a vfp thumbcallconvention-hard cortexa5" TARGET_FPU= "hard" meta meta-poky meta-yocto-bsp= "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab" meta-atmel= "krogoth:784a6a7fe94e6939325f60f4dd2cc24987ff090d" meta-skeleton = "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab" meta-oe meta-networking meta-python = "krogoth:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a" ## When entering: dpkg -i mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb I got: ## dpkg: error processing archive mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb (--install): package architecture (armhf) does not match system (armel) Errors were encountered while processing: mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb ## For me it seems that the architecture is not rightfully set. I have no idea how to fix this problem. Any ideas for that? I am patching the kernel by inserting an own devicetree file and kernel config in my own meta-layer. Maybee I got problems because of that?: @meta-atmel->layer.conf BBFILE_PRIORITY_atmel = "10" @meta_mylayer BBFILE_PRIORITY_mylayer = "6" Regards! Stefan Jaritz ESA Elektroschaltanlagen Grimma GmbH Broner Ring 30 04668 Grimma Telefon: +49 3437 9211 176 Telefax: +49 3437 9211 26 E-Mail: s.jar...@esa-grimma.de Internet: www.esa-grimma.de Geschäftsführer: Dipl.-Ing. Jörg Gaitzsch Jörg Reinker Sitz der Gesellschaft: Grimma Ust.-ID: DE 141784437 Amtsgericht: Leipzig, HRB 5159 Steuernummer: 238/108/00755 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, June 7, 2016 8:00 AM US Pacific Time
On 8/3/16 6:19 AM, Philip Balister wrote: > > On 08/02/2016 11:23 AM, Jolley, Stephen K wrote: >> Attendees: Saul, David Wolfe, Joshua, Belen, Ross, Mark, Bill >> > > >> Poky - LTS/LTM Branch >> - Community Driven >> - 2 Years >> - Companies continue to push on older branches that they are >> interested in. >> - Most patches would be in Oe-Core meta-data > This kind of jumped out at me. Can anyone explain why the Yocto Project > needs an LTS version of the reference distribution? I am glad you asked. In order for a Yocto Member to be Yocto Compatible, any changes made to Bitbake or OE-core have to be submitted to the mailing list. If I have to submit changes then is makes sense that there be a central place like a repo where these changes can live. We have this for the first year. MontaVista and I am sure other Member's support products beyond the first year. It seems natural to have a process in place to continue the behavior and work Yocto Members are required to perform to maintain Yocto compatibility. Or are you saying Yocto Compatible is only good for 1 year? It not so much having an LTS Poky as much as having LTS branches for OE core and bitbake. This means Poky would not have to be kept updated nor would the Yocto Project need to build or QA the LTS branches. As I see it, an LTS branch would only exist if there is a need and is supported by the ones who desire the LTS branch. I am sure there will be some prerequisites in doing this. I don't see this as a bad thing for the community or the Project. regards, Armin > > Philip > > >> * Team Sharing - 10 min >> RP has branch with multi-config in parallel >> - fixes various other tools >> - Distributed builds in 2.2 is unlikely due to resource constraits >> >> Thanks, >> >> Sau! >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] libatomic missing in krogoth Yocto 2.1
Hi all, I'm building core-image-minimal with Yocto 2.1 krogoth. It failed with missing libatomic. The only thing closest is libatomic-ops. meta/recipes-support/libatomic-ops/libatomic-ops_7.4.2.bb [joelz@ldt-joelz]:(krogoth)$ bitbake core-image-minimal Parsing recipes: 100% || Time: 00:02:20 Parsing of 1948 .bb files complete (0 cached, 1948 parsed). 2514 targets, 389 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'libatomic' (but /home/joelz/poky/build/../meta/recipes-core/packagegroups/ packagegroup-core-standalone-sdk-target.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'libatomic' is unbuildable, removing... Missing or unbuildable dependency chain was: ['libatomic'] NOTE: Runtime target 'packagegroup-core-standalone-sdk-target' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-standalone-sdk-target', 'libatomic'] ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'packagegroup-core-standalone-sdk-target', 'libatomic'] Summary: There were 6 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Any suggestion? Thanks, Joel -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] krogoth: quilt-native failed on Ubuntu 14
Hi All, When I build core-image-minimal using Yocto 2.1 on Ubuntu 14. It failed on quilt-native-0.64-r0 do_configure ERROR: quilt-native-0.64-r0 do_configure: no configure script found at ./configure The source directory in work area is empty. tmp/work/x86_64-linux/quilt-native/0.64-r0/quilt-0.64/ Any idea how to fix this issue? The details message: [joelz@ldt-joelz]:(krogoth)$ bitbake core-image-minimal Parsing recipes: 100% || Time: 00:02:08 Parsing of 1915 .bb files complete (0 cached, 1915 parsed). 2469 targets, 357 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION= "1.30.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "beaglebone" DISTRO= "poky" DISTRO_VERSION= "2.1.1" TUNE_FEATURES = "arm armv7a vfp neoncallconvention-hard cortexa8" TARGET_FPU= "hard" meta meta-poky meta-yocto-bsp= "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab" meta-networking meta-oe meta-python = "krogoth:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a" meta-linaro = "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab" NOTE: Preparing RunQueue NOTE: Checking sstate mirror object availability (for 895 objects) NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: quilt-native-0.64-r0 do_populate_lic: Could not copy license file /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/quilt-0.64/COPYING to /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/license-destdir/quilt-native/COPYING: [Errno 2] No such file or directory: '/home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/quilt-0.64/COPYING' *ERROR: quilt-native-0.64-r0 do_configure: no configure script found at ./configure* *ERROR: quilt-native-0.64-r0 do_configure: Function failed: do_configure (log file is located at /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_configure.29952)* ERROR: Logfile of failure stored in: /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_configure.29952 ERROR: Task 29 (/home/joelz/poky2.1/poky/build/../meta/recipes-devtools/quilt/ quilt-native_0.64.bb, do_configure) failed with exit code '1' NOTE: Tasks Summary: Attempted 6 tasks of which 4 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/joelz/poky2.1/poky/build/../meta/recipes-devtools/quilt/ quilt-native_0.64.bb, do_configure Summary: There were 7 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Host info: [joelz@ldt-joelz]:(krogoth)$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS" Thanks, Joel -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] krogoth: quilt-native failed on Ubuntu 14
On 3 August 2016 at 20:34, Joel Zhou wrote: > WARNING: quilt-native-0.64-r0 do_populate_lic: Could not copy license file > /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/quilt-0.64/COPYING > to > /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/license-destdir/quilt-native/COPYING: > [Errno 2] No such file or directory: > '/home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/quilt-0.64/COPYING' > *ERROR: quilt-native-0.64-r0 do_configure: no configure script found at > ./configure* > *ERROR: quilt-native-0.64-r0 do_configure: Function failed: do_configure > (log file is located at > /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_configure.29952)* > ERROR: Logfile of failure stored in: > /home/joelz/poky2.1/poky/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_configure.29952 > ERROR: Task 29 > (/home/joelz/poky2.1/poky/build/../meta/recipes-devtools/quilt/ > quilt-native_0.64.bb, do_configure) failed with exit code '1' > Those warnings don't look good, can you just delete your build directory entirely to be sure there's not some weird corruption going on? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [eclipse-poky][PATCH] setup.sh: change TM mirror url
It makes more sense to have everything related to eclipse in one directory under http://downloads.yoctoproject.org/eclipse so move tm/ to be a subdirectory of eclipse/ Signed-off-by: Tim Orling --- scripts/setup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/setup.sh b/scripts/setup.sh index 8b2ccd6..233309f 100755 --- a/scripts/setup.sh +++ b/scripts/setup.sh @@ -227,7 +227,7 @@ then TM_SITE="http://download.eclipse.org/tm/updates/4.0/GA"; else MAIN_SITE="http://downloads.yoctoproject.org/eclipse/mars/"; -TM_SITE="http://downloads.yoctoproject.org/tm/updates/4.0/"; +TM_SITE="http://downloads.yoctoproject.org/eclipse/tm/updates/4.0/"; DEPRECATED_SITE="http://downloads.yoctoproject.org/eclipse/luna/ftp.osuosl.org/pub/eclipse/releases/luna"; fi -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-oic][PATCH] Update for IoTivity 1.1.1
* Inspired from iotivity_1.1.0.bb.
* Tinycobor is updated to v0.2.1.
* Unused libs are dropped.
* QA checks are disabled
to support Yocto jethro base and later,
without it packaging task will fail and report this message :
ERROR: QA Issue: No GNU_HASH in the elf binary
* Security is still not emabled.
* Note this version of recipe is using upstream's git repo as source
as it's smarter for upstream/downstream cooperation
More at: https://wiki.iotivity.org/yocto .
Change-Id: Ib6f69c24434615d178ccef15cad96142e2b837aa
Cc: yocto@yoctoproject.org
Forwarded:
http://lists.iotivity.org/pipermail/iotivity-dev/2016-August/005213.html
Credit-to: Kishen Maloor
Origin: https://github.com/tizenteam/meta-oic
Signed-off-by: Philippe Coval
---
recipes-core/iotivity/iotivity_1.1.1.bb | 503
1 file changed, 503 insertions(+)
create mode 100644 recipes-core/iotivity/iotivity_1.1.1.bb
diff --git a/recipes-core/iotivity/iotivity_1.1.1.bb
b/recipes-core/iotivity/iotivity_1.1.1.bb
new file mode 100644
index 000..d47046f
--- /dev/null
+++ b/recipes-core/iotivity/iotivity_1.1.1.bb
@@ -0,0 +1,503 @@
+SUMMARY = "IoTivity framework and SDK sponsored by the Open Connectivity
Foundation."
+DESCRIPTION = "IoTivity is an open source software framework enabling seamless
device-to-device connectivity to address the emerging needs of the Internet of
Things."
+HOMEPAGE = "https://www.iotivity.org/";
+DEPENDS = "boost virtual/gettext chrpath-replacement-native expat openssl
util-linux curl glib-2.0"
+EXTRANATIVEPATH += "chrpath-native"
+SECTION = "libs"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://LICENSE.md;md5=22bf216f3077c279aed7b36b1fa9e6d1"
+
+SRCREV = "83801cb90a9b96fef2726de72f48deb7180afef6"
+TINYCBOR_SRCREV = "358a7e42ab1ed421a68e699d8d8359340bcfacbd"
+
+SRC_URI =
"git://github.com/iotivity/iotivity.git;protocol=http;nobranch=1;destsuffix=${S}
\
+
https://github.com/01org/tinycbor/archive/${TINYCBOR_SRCREV}.zip;name=tinycbor;destsuffix=${S}
\
+ https://googletest.googlecode.com/files/gtest-1.7.0.zip;name=gtest \
+
http://www.sqlite.org/2015/sqlite-amalgamation-3081101.zip;name=sqlite3 \
+ "
+SRC_URI[gtest.md5sum] = "2d6ec8ccdf5c46b05ba54a9fd1d130d7"
+SRC_URI[gtest.sha256sum] =
"247ca18dd83f53deb1328be17e4b1be31514cedfc1e3424f672bf11fd7e0d60d"
+
+SRC_URI[tinycbor.md5sum] = "906cd113e90515240d62bd185c714cc6"
+SRC_URI[tinycbor.sha256sum] =
"b5b002f5540e44c995ee57c62604e85c32525b79fb720dceb422265e80aa9cba"
+
+SRC_URI[sqlite3.md5sum] = "94907e831502e2080b76e281cfa24dde"
+SRC_URI[sqlite3.sha256sum] =
"a3b0c07d1398d60ae9d21c2cc7f9be6b1bc5b0168cd94c321ede9a0fce2b3cd7"
+
+inherit scons
+
+python () {
+IOTIVITY_TARGET_ARCH = d.getVar("TARGET_ARCH", True)
+EXTRA_OESCONS = "TARGET_OS=yocto TARGET_ARCH=" + IOTIVITY_TARGET_ARCH + "
RELEASE=1 WITH_RD=1 ROUTING=GW"
+d.setVar("EXTRA_OESCONS", EXTRA_OESCONS)
+d.setVar("IOTIVITY_TARGET_ARCH", IOTIVITY_TARGET_ARCH)
+}
+
+IOTIVITY_BIN_DIR = "/opt/iotivity"
+IOTIVITY_BIN_DIR_D = "${D}${IOTIVITY_BIN_DIR}"
+
+do_compile_prepend() {
+if [ ! -f "${S}/extlibs/sqlite3/sqlite3.c" ]; then
+cp ${WORKDIR}/sqlite-amalgamation-3081101/sqlite3.c
${S}/extlibs/sqlite3
+cp ${WORKDIR}/sqlite-amalgamation-3081101/sqlite3.h
${S}/extlibs/sqlite3
+fi
+if [ ! -d "${S}/extlibs/gtest/gtest-1.7.0/" ]; then
+cp -rf ${WORKDIR}/gtest-1.7.0 ${S}/extlibs/gtest/
+fi
+
+if [ ! -d "${S}/extlibs/tinycbor/tinycbor" ] ; then
+cp -rf ${WORKDIR}/tinycbor-* ${S}/extlibs/tinycbor/tinycbor
+fi
+
+
+export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}"
+export PKG_CONFIG="PKG_CONFIG_SYSROOT_DIR=\"${PKG_CONFIG_SYSROOT_DIR}\"
pkg-config"
+}
+
+make_dir() {
+install -d $1
+}
+
+copy_file() {
+install -c -m 444 $1 $2
+}
+
+copy_exec() {
+install -c -m 555 $1 $2
+}
+
+copy_file_recursive() {
+cd $1 && find . -type d -exec install -d $2/"{}" \;
+cd $1 && find . -type f -exec install -c -m 444 "{}" $2/"{}" \;
+}
+
+copy_exec_recursive() {
+cd $1 && find . -executable -exec install -c -m 555 "{}" $2/"{}" \;
+}
+
+do_install() {
+make_dir ${D}${libdir}
+#Resource
+#C++ APIs
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc.so
${D}${libdir}
+
+#Logger
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc_logger.so
${D}${libdir}
+copy_file
${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc_logger_core.so
${D}${libdir}
+
+#CSDK Shared
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboctbstack.so
${D}${libdir}
+
+#CSDK Static
+copy_file
${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/libconnectivity_abstraction.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/libcoap.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboctbstack.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/lib
