Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
It's picking up the minimal image instead of full-cmdline? Can you try: runqemu tmp/deploy/images/qemux86/ or runqemu qemux86 core-image-full-cmdline Thanks, Anuj On Fri, 2019-05-10 at 06:46 +, AshishKumar Mishra wrote: > HI Members , > Good Afternoon. > > I am trying to recompile the kernel after changing kernel-config > option and then recompile the kernel using below mentioned steps > 1) bitbake -c menuconfig virtual/kernel > 2) bitbake -c diffconfig virtual/kernel ( copy the config- > fragment to ~/Desktop) > 3) bitbake -C deploy linux-yocto ( to recompile kernel ) > 4) runqemu qemux86 > > The timestamp of files in tmp/deploy/images/qemux86/* is updated > properly but the time shown by command "uname -a" always shows > older time & is not showing recently compiled times. > > I checked the kernel config options in image , i can see the changes > i did > from menuconfig , but not sure / confused as to why the time shown > by "uname -a" is not getting updated. > > Basically i am trying to change some kernel-config & check if the > compiled > kernel is getting updated or not. > > Attached along are the snapshot for the error. > > Can members please let me know what am i doing wrong here or missing, > > Thanks > Ashish. > > > > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
HI Anuj , I was building minimal image using $ bitbake core-image-minimal haven't tried full-cmdline. Not able to track why kernel "uname" has older timestamp rather than the one from build/deploy/image as seen by "ls -al Am i missing any command or sequence here -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto image systemd debugging
Hi Lukasz, > What do you mean by debug? > In most cases 'systemctl status ', 'systemctl --failed', > system-analyze > and journalctl are efficient. Sometimes I set > 'StandardOutput=journal+console' > in service file to just see output during booting. There is an ofono.service which failed by systemd service, but there were no problems if I start it manually, the systemctl status ', 'systemctl --failed' told me it failed but did not tell me why it was failed and what was the cause. Hence I asked how to debug it, I guess your advice is to change following ofono.service StandardError='journal+console', correct? cat /lib/systemd/system/ofono.service [Unit] Description=Telephony service After=syslog.target [Service] Type=dbus BusName=org.ofono ExecStart=/usr/sbin/ofonod -n StandardError=null [Install] WantedBy=multi-user.target Thank you. Kind regards, - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] apparmor: fetch from git
Tarballs from archive.ubuntu.com can and do disappear (similar to
archive.debian.org).
Signed-off-by: Alexander Kanavin
---
recipes-mac/AppArmor/apparmor_2.13.2.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.2.bb
b/recipes-mac/AppArmor/apparmor_2.13.2.bb
index 62ed611..4eaec00 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.2.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.2.bb
@@ -14,7 +14,7 @@ LIC_FILES_CHKSUM =
"file://${S}/LICENSE;md5=fd57a4b0bc782d7b80fd431f10bbf9d0"
DEPENDS = "bison-native apr gettext-native coreutils-native"
SRC_URI = " \
-
http://archive.ubuntu.com/ubuntu/pool/main/a/${BPN}/${BPN}_${PV}.orig.tar.gz \
+
git://gitlab.com/apparmor/apparmor.git;protocol=https;branch=apparmor-2.13 \
file://disable_perl_h_check.patch \
file://crosscompile_perl_bindings.patch \
file://apparmor.rc \
@@ -24,8 +24,8 @@ SRC_URI = " \
file://run-ptest \
"
-SRC_URI[md5sum] = "2439b35266b5a3a461b0a2dba6e863c3"
-SRC_URI[sha256sum] =
"844def9926dfda5c7858428d06e44afc80573f9706458b6e7282edbb40b11a30"
+SRCREV = "af4808b5f6b58946f5c5a4de4b77df5e0eae6ca0"
+S = "${WORKDIR}/git"
PARALLEL_MAKE = ""
--
2.17.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto image systemd debugging
On Friday, May 10, 2019 10:09 AM, JH wrote: > > What do you mean by debug? > > In most cases 'systemctl status ', 'systemctl --failed', > > system-analyze and journalctl are efficient. Sometimes I set > > 'StandardOutput=journal+console' > > in service file to just see output during booting. > > There is an ofono.service which failed by systemd service, but there were > no problems if I start it manually, the systemctl status ', > 'systemctl --failed' told me it failed but did not tell me why it was failed > and what was the cause. Hence I asked how to debug it, I guess your advice > is to change following ofono.service StandardError='journal+console', correct? > > cat /lib/systemd/system/ofono.service > [Unit] > Description=Telephony service > After=syslog.target > > [Service] > Type=dbus > BusName=org.ofono > ExecStart=/usr/sbin/ofonod -n > StandardError=null > > [Install] > WantedBy=multi-user.target > Yes, please set: StandardError=journal+console Best regards, Lukasz Zemla *** The information in this email is confidential and intended solely for the individual or entity to whom it is addressed. If you have received this email in error please notify the sender by return e-mail, delete this email, and refrain from any disclosure or action based on the information. *** -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
On 5/10/19 12:10 AM, AshishKumar Mishra wrote: HI Anuj , I was building minimal image using $ bitbake core-image-minimal haven't tried full-cmdline. Not able to track why kernel "uname" has older timestamp rather than the one from build/deploy/image as seen by "ls -al Am i missing any command or sequence here uname will show the time when it was built, which might be different time then the one when it was copied over to deploy. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [OE-core][RFC][PATCH] Remove irda-utils and the irda feature
IrDA support was removed in kernel 4.17.
Signed-off-by: Adrian Bunk
---
documentation/ref-manual/ref-features.xml | 4 -
meta-poky/conf/distro/poky-tiny.conf | 2 +-
.../distro/include/default-distrovars.inc | 2 +-
meta/conf/distro/include/maintainers.inc | 1 -
.../irda-utils/irda-utils-0.9.18/init | 78 -
.../irda-utils-0.9.18/ldflags.patch | 87 ---
.../irda-utils/irda-utils-0.9.18/musl.patch | 29 ---
.../irda-utils/irda-utils_0.9.18.bb | 51 ---
.../packagegroups/packagegroup-base.bb| 19
9 files changed, 2 insertions(+), 271 deletions(-)
delete mode 100755 meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/init
delete mode 100644
meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.patch
delete mode 100644
meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/musl.patch
delete mode 100644 meta/recipes-connectivity/irda-utils/irda-utils_0.9.18.bb
diff --git a/documentation/ref-manual/ref-features.xml
b/documentation/ref-manual/ref-features.xml
index 7a3555d0b9..b057d2d040 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -76,8 +76,6 @@
ext2: Hardware HDD or
Microdrive
-irda: Hardware has IrDA
support
-
keyboard: Hardware has a
keyboard
pcbios: Support for
booting through BIOS
@@ -190,8 +188,6 @@
support.
ipv6: Include IPv6
support.
-irda: Include IrDA
support.
-
keyboard: Include keyboard
support (e.g. keymaps will be loaded during boot).
diff --git a/meta-poky/conf/distro/poky-tiny.conf
b/meta-poky/conf/distro/poky-tiny.conf
index a82d043e48..1f8b6e8ff3 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/conf/distro/poky-tiny.conf
@@ -60,7 +60,7 @@ USE_NLS="no"
# Comment out any of the lines below to disable them in the build
# DISTRO_FEATURES options:
-# alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci
+# alsa bluetooth ext2 pcmcia usbgadget usbhost wifi nfs zeroconf pci
DISTRO_FEATURES_TINY = "pci"
DISTRO_FEATURES_NET = "ipv4 ipv6"
DISTRO_FEATURES_USB = "usbhost"
diff --git a/meta/conf/distro/include/default-distrovars.inc
b/meta/conf/distro/include/default-distrovars.inc
index 7a0baf3260..10d86cf7b1 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -10,7 +10,7 @@ LOCALE_UTF8_ONLY ?= "0"
LOCALE_UTF8_IS_DEFAULT ?= "1"
LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
-DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 ipv4 ipv6 irda
largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
+DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 ipv4 ipv6 largefile
pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
IMAGE_FEATURES ?= ""
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 00b7914fff..8d72f52e3e 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -286,7 +286,6 @@ RECIPE_MAINTAINER_pn-intltool = "Alexander Kanavin
"
RECIPE_MAINTAINER_pn-iproute2 = "Changhyeok Bae "
RECIPE_MAINTAINER_pn-iptables = "Changhyeok Bae "
RECIPE_MAINTAINER_pn-iputils = "Changhyeok Bae "
-RECIPE_MAINTAINER_pn-irda-utils = "Changhyeok Bae "
RECIPE_MAINTAINER_pn-iso-codes = "Alexander Kanavin "
RECIPE_MAINTAINER_pn-iw = "Changhyeok Bae "
RECIPE_MAINTAINER_pn-libjpeg-turbo = "Anuj Mittal "
diff --git a/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/init
b/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/init
deleted file mode 100755
index 6f29e9c6ed..00
--- a/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/init
+++ /dev/null
@@ -1,78 +0,0 @@
-#! /bin/sh
-### BEGIN INIT INFO
-# Provides: irda
-# Required-Start:$network $remote_fs
-# Required-Stop: $network $remote_fs
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Infrared port support
-### END INIT INFO
-
-NAME="irattach"
-test -x "$IRDA_DAEMON" || IRDA_DAEMON=/usr/sbin/irattach
-test -z "$IRATTACH_PID" && IRATTACH_PID=/var/run/irattach.pid
-
-# Source function library.
-. /etc/init.d/functions
-
-module_id() {
-awk 'BEGIN { FS=": " } /Hardware/ { print $2 } ' &2
- exit 1
- ;;
-esac
diff --git
a/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.patch
b/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.patch
deleted file mode 100644
index b246de8f5f..00
--- a/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.p
[yocto] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)
What: 30-minute network outage to Portland-hosted services When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC) Why : Network equipment replacement by our service provider Services Impacted: autobuilder.yoctoproject.org, downloads.yoctoproject.org, sstate.yoctoproject.org Our Portland hosting provider needs to replace some of their main network equipment, which will require rerunning some cables. They are asking us to prepare for up to a 30-minute network outage between the hours listed above in order to complete this work. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Replacing a configuration file from another recipe
On 4/29/19 5:35 AM, Damien LEFEVRE wrote: Hi, In our base image we use nginx. I created a nginx.bbappend to add our PHP configuration in a separated layer. For a specific variant of the image I need to add an extra bit of nginx configuration. I though I could create a new recipe to overwrite nginx.conf and include that recipe in the variant image definition, but bitbake shouts at me that I cannot modify a file from another recipe. If that's the case, is it possible to create image name based bbappend files? Or do I need to create a separate nginx overwrite layer with higher priority than the base image nginx.bbappend for that image variant? (I wouldn't like that) you might want to use a function to get this done and add it to IMAGE_POSTPROCESS_COMMAND in the specific image recipe. Thanks, -Damien -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] I can't make a minimal example for Bitbake version 1.42
I made a simple bitbake example - hello world. An example is here: https://github.com/GeraPesikoff/bitbake-hello-world With the bitbake version 1.40, everything works fine, but with version 1.42, the execution ends with an error: ERROR: An uncaught exception occurred in runqueue | ETA: 0:00:00 Traceback (most recent call last): File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1513, in RunQueue.execute_runqueue(): try: return self._execute_runqueue() except bb.runqueue.TaskFailure: File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1433, in RunQueue._execute_runqueue(): [43, 967, 4, 3, 1, 5, 3, 7, 13, 1, 2, 1, 1, 246, 35, 1, 38, 1, 35, 2, 338, 204, 142, 3, 3, 37, 244]) if self.rqdata.prepare() == 0: self.state = runQueueComplete File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1169, in RunQueueData.prepare(): todeal.remove(tid) self.prepare_task_hash(tid) File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1182, in RunQueueData.prepare_task_hash(tid='/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb:do_build'): self.runtaskentries[tid].hash = bb.parse.siggen.get_taskhash(taskfn, taskname, procdep, self.dataCaches[mc]) self.runtaskentries[tid].unihash = bb.parse.siggen.get_unihash(taskfn + "." + taskname) File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/siggen.py", line 45, in SignatureGenerator.get_unihash(task='/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb.do_build'): def get_unihash(self, task): return self.taskhash[task] KeyError: '/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb.do_build' ERROR: Running idle function Traceback (most recent call last): File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1513, in RunQueue.execute_runqueue(): try: return self._execute_runqueue() except bb.runqueue.TaskFailure: File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1433, in RunQueue._execute_runqueue(): [43, 967, 4, 3, 1, 5, 3, 7, 13, 1, 2, 1, 1, 246, 35, 1, 38, 1, 35, 2, 338, 204, 142, 3, 3, 37, 244]) if self.rqdata.prepare() == 0: self.state = runQueueComplete File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1169, in RunQueueData.prepare(): todeal.remove(tid) self.prepare_task_hash(tid) File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/runqueue.py", line 1182, in RunQueueData.prepare_task_hash(tid='/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb:do_build'): self.runtaskentries[tid].hash = bb.parse.siggen.get_taskhash(taskfn, taskname, procdep, self.dataCaches[mc]) self.runtaskentries[tid].unihash = bb.parse.siggen.get_unihash(taskfn + "." + taskname) File "/home/gera/research/bitbake/bitbake-1.42/lib/bb/siggen.py", line 45, in SignatureGenerator.get_unihash(task='/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb.do_build'): def get_unihash(self, task): return self.taskhash[task] KeyError: '/home/gera/research/bitbake/bbTutorial/build/../meta-tutorial/recipes-tutorial/first/first_0.1.bb.do_build' Summary: There were 13 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Tell me please, what's the problem? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
