Re: Included conf files in our receipes.
NIKHIL PATIL
Hi , 1) U mean that , i need to create for eg. core-image-nikhil.bb and inside that i need to give IMAGE_INSTALL_APPEND = "minicom" right ? 2) Before we are including meta layers in bblayer.conf . but any other file so we can include our new meta layers (for eg . meta-test ) ?
On Thu, Oct 22, 2020 at 3:09 PM Alexander Kanavin <alex.kanavin@...> wrote:
|
|
Re: Included conf files in our receipes.
Alexander Kanavin
You should make a new image recipe, and define what goes into it there. Alex
On Thu, 22 Oct 2020 at 11:03, NIKHIL PATIL <nikhilvp29@...> wrote:
|
|
Included conf files in our receipes.
NIKHIL PATIL
Hi Team , We are using yocto sdk for intel leafhill board. For our development purpose we are changing in local.conf. (for eg. if i want minicom package means we are doing IMAGE_INSTALL_APPEND += "minicom" ). But , As per requirement we dont want these ( means adding in local.conf and bblayer.conf ) , so every needed packages (eg. minicom) how we can add packages in our meta-layer (like eg. meta-test ) . so all required packages will come with our core image . how we can achieve these ?
|
|
Re: readonly rootfs -> make files writable
Yocto
Sent via BlackBerry Hub+ Inbox for Android
Original Message From: marek.belisko@gmail.com Sent: October 22, 2020 12:53 To: yocto@yoctoproject.org Subject: [yocto] readonly rootfs -> make files writable Hi, I'm using the read-only rootfs feature on my system, but for some packages which I'm integrating it makes trouble. I used volatile-binds recipe to mount changes in overlayfs (on other partition) but after reboot files are lost (when mount volatile directory). Another approach which came to my mind is to symlink all files/dirs to other partitions but to me it looks like overkill. Exists there some other mechanism I can use to keep file preserved and still have readonly rootfs functionality? Thanks and BR, Sounds like os-tree could be a good option here with immutable rootfs marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
|
|
readonly rootfs -> make files writable
Marek Belisko
Hi,
I'm using the read-only rootfs feature on my system, but for some packages which I'm integrating it makes trouble. I used volatile-binds recipe to mount changes in overlayfs (on other partition) but after reboot files are lost (when mount volatile directory). Another approach which came to my mind is to symlink all files/dirs to other partitions but to me it looks like overkill. Exists there some other mechanism I can use to keep file preserved and still have readonly rootfs functionality? Thanks and BR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
|
|
Re: [meta-zephyr][PATCH] qemu-cortex-m3.conf: Disable RNG passthrough
On Wed, Oct 21, 2020 at 12:13 AM Naveen Saini
<naveen.kumar.saini@intel.com> wrote: this looks fine. ARCH_qemu-cortex-m3 = "arm"
|
|
Re: dnf error coming while compiling core-image-sato image.
Yocto
On 10/21/20 5:38 PM, NIKHIL PATIL
wrote:
mmm nope... Build Configuration:
|
|
Re: dnf error coming while compiling core-image-sato image.
NIKHIL PATIL
Hi team , I am assuming in local.conf we used DISTRO ?= "poky" and DISTRO = "poky-sota-systemd" both thats why we are getting these error or what ?
On Wed, Oct 21, 2020 at 10:30 AM Yocto <yocto@...> wrote:
|
|
[meta-zephyr][PATCH v2] zephyr: use TCLIBC=newlib directly
Ross Burton
Instead of setting TCLIBC=3Dbaremetal and then adding newlib in various p=
laces, just set TCLIBC=3Dnewlib directly. This also means we can use the standard DEPENDS instead of reinventing th= em. Signed-off-by: Ross Burton <ross.burton@arm.com> --- conf/distro/zephyr.conf | 7 +------ recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 5 +---- 2 files changed, 2 insertions(+), 10 deletions(-) diff --git a/conf/distro/zephyr.conf b/conf/distro/zephyr.conf index 44448af..a98da32 100644 --- a/conf/distro/zephyr.conf +++ b/conf/distro/zephyr.conf @@ -5,16 +5,11 @@ DISTRO_VERSION =3D "1.0" =20 TARGET_VENDOR =3D "-yocto" =20 -TCLIBC =3D "baremetal" -TCLIBCAPPEND =3D "" +TCLIBC =3D "newlib" =20 TEST_TARGET =3D "QemuTargetZephyr" TEST_SUITES =3D "zephyr" =20 -PREFERRED_PROVIDER_virtual/libc =3D "newlib" -PREFERRED_PROVIDER_virtual/libiconv =3D "newlib" - -TOOLCHAIN_TARGET_TASK +=3D " newlib" INHERIT +=3D "siteinfo-zephyr" =20 INHERIT +=3D "uninative" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/reci= pes-kernel/zephyr-kernel/zephyr-kernel-common.inc index 7fa4b25..3f82c20 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -19,10 +19,7 @@ EXTRA_OECMAKE_append_arm =3D " -DZEPHYR_MODULES=3D${S}= /modules/cmsis" export ZEPHYR_BASE=3D"${S}" =20 =20 -# We always need a toolchain to cross-compile. -INHIBIT_DEFAULT_DEPS =3D "1" -DEPENDS +=3D "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} g= perf-native" -DEPENDS +=3D " python3-pyelftools-native python3-pyyaml-native python3-p= ykwalify-native" +DEPENDS +=3D "gperf-native python3-pyelftools-native python3-pyyaml-nati= ve python3-pykwalify-native" CROSS_COMPILE =3D "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}" =20 DEPENDS_append_qemuall =3D " qemu-native qemu-helper-native" --=20 2.25.1
|
|
[meta-zephyr][PATCH] qemu-cortex-m3.conf: Disable RNG passthrough
Naveen Saini
Qemu system does not passthroth RNG on x86 host.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com> --- conf/machine/qemu-cortex-m3.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/qemu-cortex-m3.conf b/conf/machine/qemu-cortex-m3.conf index dd1ce56..3a50796 100644 --- a/conf/machine/qemu-cortex-m3.conf +++ b/conf/machine/qemu-cortex-m3.conf @@ -12,5 +12,6 @@ QB_SYSTEM_NAME = "qemu-system-arm" QB_MACHINE = "-machine lm3s6965evb" QB_OPT_APPEND = "-nographic -vga none" QB_CPU = "-cpu cortex-m3" +QB_RNG = "" ARCH_qemu-cortex-m3 = "arm" -- 2.17.1
|
|
[meta-cgl][PATCH] heartbeat: don't use trailing slash in S
Yu, Mingli
From: Mingli Yu <mingli.yu@windriver.com>
* see oe-core base.bbclass changes from: https://lists.openembedded.org/g/openembedded-core/message/143159 https://lists.openembedded.org/g/openembedded-core/message/143161 Signed-off-by: Mingli Yu <mingli.yu@windriver.com> --- meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb index 35fee43..5031c64 100644 --- a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb +++ b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb @@ -38,7 +38,7 @@ SRC_URI = " \ " SRC_URI[md5sum] = "101c8f507b1f407468d5ef15ae6719da" SRC_URI[sha256sum] = "851d2add2c129fef9fede764fec80229e1f6e7295e0e979950d10258648b462c" -S = "${WORKDIR}/Heartbeat-3-0-958e11be8686/" +S = "${WORKDIR}/Heartbeat-3-0-958e11be8686" DEPENDS = "cluster-glue corosync gnutls libxslt-native xmlto-native docbook-xml-dtd4-native docbook-xsl-stylesheets-native intltool" RDEPENDS_${PN} += "python" inherit autotools-brokensep pkgconfig useradd -- 2.17.1
|
|
Re: [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly
Naveen Saini
Few kernel testcases have dependencies on gperf-native, so we should keep it in DEPENDS.
toggle quoted messageShow quoted text
Regards, Naveen
-----Original Message-----
From: Ross Burton <ross.burton@arm.com> Sent: Tuesday, October 20, 2020 8:43 PM To: yocto@lists.yoctoproject.org Cc: Saini, Naveen Kumar <naveen.kumar.saini@intel.com> Subject: [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly Instead of setting TCLIBC=baremetal and then adding newlib in various places, just set TCLIBC=newlib directly. This also means we can use the standard DEPENDS instead of reinventing them. Signed-off-by: Ross Burton <ross.burton@arm.com> --- conf/distro/zephyr.conf | 7 +------ recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 3 --- 2 files changed, 1 insertion(+), 9 deletions(-) diff --git a/conf/distro/zephyr.conf b/conf/distro/zephyr.conf index 44448af..a98da32 100644 --- a/conf/distro/zephyr.conf +++ b/conf/distro/zephyr.conf @@ -5,16 +5,11 @@ DISTRO_VERSION = "1.0" TARGET_VENDOR = "-yocto" -TCLIBC = "baremetal" -TCLIBCAPPEND = "" +TCLIBC = "newlib" TEST_TARGET = "QemuTargetZephyr" TEST_SUITES = "zephyr" -PREFERRED_PROVIDER_virtual/libc = "newlib" -PREFERRED_PROVIDER_virtual/libiconv = "newlib" - -TOOLCHAIN_TARGET_TASK += " newlib" INHERIT += "siteinfo-zephyr" INHERIT += "uninative" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index 7fa4b25..b947472 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -19,9 +19,6 @@ EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis" export ZEPHYR_BASE="${S}" -# We always need a toolchain to cross-compile. -INHIBIT_DEFAULT_DEPS = "1" -DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native" DEPENDS += " python3-pyelftools-native python3-pyyaml-native python3-pykwalify-native" CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}" -- 2.25.1
|
|
Re: dnf error coming while compiling core-image-sato image.
Yocto
On 10/20/20 8:06 PM, NIKHIL PATIL
wrote:
I can confirm that Ive also seen this trying to build in the
Yocto build appliance I downloaded yesterday....
|
|
Re: dnf error coming while compiling core-image-sato image.
NIKHIL PATIL
Hi team, I am not able compile a core-image-minimal also. same issue facing here. PFA (local.conf) .
On Tue, Oct 20, 2020 at 7:50 PM Randy MacLeod <randy.macleod@...> wrote: On 2020-10-20 9:06 a.m., NIKHIL PATIL wrote:
|
|
Re: QA notification for completed autobuilder build (yocto-3.2.rc1)
Sangeeta Jain
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion is next Monday, October 26. Thanks, Sangeeta
-----Original Message-----
|
|
Let me tell you how I really feel. Zero filter. If you need meta-python2, you need to become a maintainer. Immediately. Period.
Tim Orling
I have absolutely no need for python2, I made this abundantly clear when I created the meta-python2 layer. If you depend upon continuing support of python2 via the meta-python2 layer, this is your call to arms. I was originally intending to abdicate any support after the 3.1 "dunfell" release, but managed to somehow continue supporting it into the crest of the 3.2 "gatesgarth" release. I will stop all support and actively refuse lo respond to any emails and this layer will be dead and I have zero care in the world that it stops being useful. I do not use it. I do not depend upon it. You are not paying me to do this. You cannot pay me enough to do this. Period. Support yourself. If this is not clear enough, I am happy to have a virtual video call with you that you will not like. --moto-timo
|
|
Re: Using RDEPENDS in bbappend files to install additional packages?
Apologies for the marginally related reply, but the provided example triggered a reminder of a best practice we started doing that had some significant maintainability benefits. Instead of this pattern: RDEPENDS_${PN} += " \ lighttpd-module-alias \ lighttpd-module-auth \ lighttpd-module-cgi \ lighttpd-module-compress \ lighttpd-module-evasive \ lighttpd-module-evhost \ We found that this pattern made it significantly easier to manage recipes, as well as use common command line tools like grep/sed/awk, without having to deal with the complexities of multi-line processing. It also helped make git commits and patches much more focused and readable. RDEPENDS_${PN} += " lighttpd-module-alias" RDEPENDS_${PN} += " lighttpd-module-auth" RDEPENDS_${PN} += " lighttpd-module-cgi" RDEPENDS_${PN} += " lighttpd-module-compress" RDEPENDS_${PN} += " lighttpd-module-evasive" RDEPENDS_${PN} += " lighttpd-module-evhost"
On Mon, Oct 19, 2020 at 6:12 AM Quentin Schulz <quentin.schulz@...> wrote: Hi Robert, -- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
|
Re: [meta-zephyr][PATCH] zephyr: use TCLIBC=newlib directly
On 10/20/20 5:42 AM, Ross Burton wrote:
Instead of setting TCLIBC=baremetal and then adding newlib in various places,I think this will also link the app with newlib now which previously was using baremetal. Signed-off-by: Ross Burton <ross.burton@arm.com>
|
|
Re: [meta-zephyr][PATCH] README: add patch submission details
On 10/20/20 3:04 AM, Ross Burton wrote:
---Can we use markdown syntax and call it README.md ? this helps with other infras like gitlab and github where this might be cloned to @@ -69,4 +69,15 @@ or
|
|
QA notification for completed autobuilder build (yocto-3.2.rc1)
pokybuild@...
A build flagged for QA (yocto-3.2.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc1 Build hash information: bitbake: 9345d257ced432adc2d16af20ace58cc7c086aab meta-arm: b419151acd2761d0e2723f0d0c0bbbed00c45c5b meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43 meta-intel: 0e4b3cb01735bdc5ebf50c547927f1f59b0248d2 meta-kernel: dbf8bdfa6683404e5071feb47ef6aa347cab1b01 meta-mingw: d2809d7c93bdb46014e1f8b3b0a4f42030078905 oecore: ea8ba9a15bcec7f5fbce1f40170298f87a808249 poky: 4e4a302e37ac06543e9983773cdb4caf7728330d This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@linuxfoundation.org
|
|