Date   

Re: Run an executable script on the yocto image

Konrad Weihmann <kweihmann@...>
 

If you're sure you only use standard python libs it's fairly easy.

make a recipe (name it how ever you like)

SCR_URI = "file://<your script>.py"

do_install() {
install -m 0755 <your script>.py ${bindir}/<your script>.py
}

RDEPENDS:${PN} += "python3-core"

in the image

IMAGE_INSTALL += "<your recipe name>"

---

if your script needs further libraries, reference them in the recipe with

RDEPENDS:${PN} += "python3-core dependency1 dependency2 dependency3..."

Then you call the result on your device with <your script>.py from any console

Maybe add a "#!/usr/bin/env python3" shebang as a first line to your script

On 26.08.21 17:14, yasminebenghozzi6@... wrote:
Hello,
Can anyone suggest how to make a python script executable on the yocto image? I 've been trying with the pyinstaller but didn't work, I made it executable on my laptop and transfer it to yocto image but didn't work also,
Has any one tried it before? are there other alternatives?


Run an executable script on the yocto image

yasminebenghozzi6@...
 

Hello, 

Can anyone suggest how to make a python script executable on the yocto image? I 've been trying with the pyinstaller but didn't work, I made it executable on my laptop and transfer it to yocto image but didn't work also, 
Has any one tried it before? are there other alternatives? 


Yocto Autobuilder: Latency Monitor and AB-INT - Meeting notes: Aug 26, 2021

Randy MacLeod
 

YP AB Intermittent failures meeting
===================================
Aug 26, 2021, 9 AM ET
https://windriver.zoom.us/j/3696693975

Attendees: Tony, Richard, Trevor, Randy, Alex, Saul, Sakib!


Summary:
========

It was a rough week for testing due to glibc-2.34 and rust
problems so we'll see if the next week let's us return to:
ptest results continue to improve but there's still room
for even more improvement.

The make/ninja load average limit is in but it's not clear
if it's effective yet and it breaks dunfell. Trevor investigating
(Aug 26!).

There's not much new this week, I've commented on a few existing
activities below and added "Aug 26" in most cases.


If anyone wants to help, we could use more eyes on the logs,
particularly the summary logs and understanding iostat #
when the dd test times out.



Plans for the week:
===================

Richard: biking and wait for QA results for M3.
Alex: SWAT plans. September email, training. libevent monotonic fix!
Sakib: hook more responsive load average in to latency test. (v3)
Trevor: patch to set PARALLEL_MAKE : -l 50
-> dunfell, gatesgarth, hardknott (Aug 5 - it's a priority)
Investigate dunfell which failed with this change.
- data on WR AB load average.
Saul: none
Randy: Gather more iostat data, graph it!

Meeting Notes:
==============

1. job server

- ninja could be patched with make's more responsive algorithm
next or is this good enough?

Aug 26:
Randy made some graphs that show that the -l NUM results
in the number of compile jobs oscillates *wildly* between 0 and 200
on a 192 core builder compiling chromium. What I did was:
$ bitbake -c cleansstate chromium-x11
$ bitbake -c configure chromium-x11
$ bitbake -c compile chromium-x11
and while that compile was running:
$ while [ ! -f /tmp/compiling-chromium-is-done ]; do \
cat /proc/loadavg >> procs-load.log ; sleep 0.5 ;
done
Results so far:
https://postimg.cc/gallery/3hjfYfG/f8f46c97
Next step is either:
a. collect data as above for an image build and see if the sub-optimal
ninja behaviour makes a difference
and/or
b. patch ninja with make's more responsive load avg
algorithm:
https://git.savannah.gnu.org/cgit/make.git/commit/?id=d8728efc8


- Richard suggested that we extract make's code for measuring the load
average to a separate binary and run it in the periodic io latency
test. Also can we translate it to python?
- Trevor is working on this and had some problems so next week.
(Aug 19 - Trevor is back from vaction so maybe next week.)

- Trevor to see if the load average change really did reduce load
on WR build systems. (Aug 19)

2. AB status

Trevor is learning about buildbot and working on a scheduling bug
(CentOS worker?)

bitbake layer setup tool should allow multiple backends:
eg: kas, a y-a-helper.

ptest cases are improving, we may be close to done!
Let's wait a week to see how things go.
(July29, Aug 5, Aug 19, we're not done...)

- lttng-tools ptest is failing. RP is working on it with upstream.
The timeout (done on Aug 5) increase hasn't helped.


3. Sakib's improvements to the logging are merged.

Sakib generated a summary of all high latency 'top' logs from
~July 23->July 29 by just running his summary script on the
merged raw top logs.

More analysis required....


Still relevant parts of
Previous Meeting Notes:
=======================


4. bitbake server timeout ( no change july 29, Aug 19)

"Timeout while waiting for a reply from the bitbake server (60s)"

5. io stalls (no update: July 29)

Richard said that it would make sense to write an ftrace utility
/ script to monitor io latency and we could install it with sudo
Ch^W mentioned ftrace on IRC.
Sakib and Randy will work on that but not for a week or two
or longer! (Aug 19).

Randy collected iostat data on 3 build server:
https://postimg.cc/gallery/8cN6LYB
We agreed that having -ty-2 be ~ 100 utilization for many hours
in a row is not acceptable and that a threshold of ~ 10 minutes
at 100% utilization may be a reasonable limt. I need to figure out
if I can get data on the fraction of IO done per IO clas since
we do use ionice to do clean-up and other activities.


../Randy


Re: Parserror while building the image #yocto

Martin Jansa
 

Update bitbake to support new overrides syntax.


On Thu, Aug 26, 2021 at 3:28 PM <yasminebenghozzi6@...> wrote:
I got this error while trying to build the image after checking out the timo/python3-pyinstaller.
ERROR: ParseError at /home/yasmine/yocto/poky/meta-openembedded/meta-oe/conf/layer.conf:106: unparsed line: 'DEFAULT_TEST_SUITES:pn-meta-oe-ptest-image = "${PTESTTESTSUITE}"'
 




Parserror while building the image #yocto

yasminebenghozzi6@...
 

I got this error while trying to build the image after checking out the timo/python3-pyinstaller.
ERROR: ParseError at /home/yasmine/yocto/poky/meta-openembedded/meta-oe/conf/layer.conf:106: unparsed line: 'DEFAULT_TEST_SUITES:pn-meta-oe-ptest-image = "${PTESTTESTSUITE}"'
 


Re: Dependencies are not resolved correctly when building the SDK

asconcepcion
 

Please post the exact error that you're getting.
Sorry, I haven't posted the exact error because I thought it is quite specific to the recipe I'm building. My first question was also too vague, sorry for that. The problem is that it fails in building that package because of a missing file that should be populated by that dependency.

The error happens in the do_compile task:

| make[1]: *** No rule to make target 'm4_image.bin', needed by 'flash_linux_m40'.  Stop.                                                                                                                             
| make: *** [Makefile:23: flash_linux_m40] Error 2                                                                                                                                                                    
| WARNING: exit code 2 from a shell command.
So, the package expects that the file 'm4_image.bin' exists, and this file is generated by the dependency (it works well when building the yocto image, but not when building the SDK from scratch).

Thanks,
Alejandro


Re: Dependencies are not resolved correctly when building the SDK

Anuj Mittal
 

On Thu, 2021-08-26 at 00:44 -0700, asconcepcion wrote:
Hi Anuj,

Thanks for the tip. I added "BBCLASSEXTEND += "nativesdk"" to the
recipe of the dependency package, but I still get the same error. Do
you know if I could be missing something else?
Please post the exact error that you're getting.

Thanks,

Anuj


Re: Dependencies are not resolved correctly when building the SDK

asconcepcion
 

Hi Anuj,

Thanks for the tip. I added "BBCLASSEXTEND += "nativesdk"" to the recipe of the dependency package, but I still get the same error. Do you know if I could be missing something else?

Thanks.
Alejandro.


Re: Dependencies are not resolved correctly when building the SDK

Anuj Mittal
 

On Wed, 2021-08-25 at 23:54 -0700, asconcepcion wrote:
Hello,

We have a custom package recipe that has a build dependency with
another one (defined in yocto with the DEPENDS variable). If we build
an image that includes that package, bitbake will build the
dependency
before building the package, as expected. However, if we build the
SDK
associated to that image (with bitbake <image> -c populate_sdk), it
will fail in building that package because of a missing dependency.
Does anyone know what could be causing this behavior?
Can that recipe for dependency package actually be built for nativesdk?

Thanks,

Anuj


Dependencies are not resolved correctly when building the SDK

asconcepcion
 

Hello,

We have a custom package recipe that has a build dependency with another one (defined in yocto with the DEPENDS variable). If we build an image that includes that package, bitbake will build the dependency before building the package, as expected. However, if we build the SDK associated to that image (with bitbake <image> -c populate_sdk), it will fail in building that package because of a missing dependency. Does anyone know what could be causing this behavior?

Thanks.


Re: # yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

Monsees, Steven C (US)
 

 

Never mind this, I worked it out…  thanks anyway.

 

From: yocto@... <yocto@...> On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Wednesday, August 25, 2021 12:25 PM
To: yocto@...
Subject: [yocto] # yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

 

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.

 

 

Using zeus, and I am build an image with no issues...

 

I then want to tweak the configuration by pulling in an a ".cfg" file to be able to tweak options depending on use…

 

I add the following to the image ".bb" file:

 

FILESEXTRAPATHS_prepend := "$THISDIR:"

SRC_URI += "file://sbcb-defaultfs-swdebug.cfg"

 

 

sbcb-defaultfs-swdebug.cfg consists of three lines:

 

CONFIG_KPROBES=y

CONFIG_KPROBES_ON_FTRACE=y

CONFIG_DEBUG_INFO=y

 

When I add the above I see the following build issue, how do I relove this ?

 

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: QA Issue: sbcb-defaultfs-swdebug: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum]

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: Fatal QA errors found, failing task.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-swdebug/1.0-r0/temp/log.do_populate_lic.29324

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_1/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-swdebug.bb:do_populate_lic) failed with exit code '1'

 

Thanks,

Steve


# yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

Monsees, Steven C (US)
 

 

Using zeus, and I am build an image with no issues...

 

I then want to tweak the configuration by pulling in an a ".cfg" file to be able to tweak options depending on use…

 

I add the following to the image ".bb" file:

 

FILESEXTRAPATHS_prepend := "$THISDIR:"

SRC_URI += "file://sbcb-defaultfs-swdebug.cfg"

 

 

sbcb-defaultfs-swdebug.cfg consists of three lines:

 

CONFIG_KPROBES=y

CONFIG_KPROBES_ON_FTRACE=y

CONFIG_DEBUG_INFO=y

 

When I add the above I see the following build issue, how do I relove this ?

 

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: QA Issue: sbcb-defaultfs-swdebug: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum]

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: Fatal QA errors found, failing task.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-swdebug/1.0-r0/temp/log.do_populate_lic.29324

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_1/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-swdebug.bb:do_populate_lic) failed with exit code '1'

 

Thanks,

Steve


using STAGING_KERNEL_DIR for compiling userspace program

Marek Belisko
 

Hi,

I'm trying to add a recipe for:
https://github.com/bootlin/libva-v4l2-request package. This library
heavily depends on actual kernel headers (see
PR.https://github.com/bootlin/libva-v4l2-request). I've bumped kernel
to 5.14-rc7 nad in recipe I'm trying to use what is suggested:

# This is how linux-libc-headers says to include custom uapi headers
CFLAGS_append += " -I ${STAGING_KERNEL_DIR}/include/uapi -I
${STAGING_KERNEL_DIR}/include "
do_configure[depends] += "virtual/kernel:do_shared_workdir"

Problem is that I see a lot of errors like:
kernel-source/include/linux/cache.h:6:10: fatal error: asm/cache.h: No
such file or directory
| 6 | #include <asm/cache.h>

or
recipe-sysroot/usr/include/bits/stdint-intn.h:27:19: note: previous
declaration of 'int64_t' was here
| 27 | typedef __int64_t int64_t;

I tried to compile this package manually on the host only difference
is that I used headers from 5.14 by make headers_install and
everything compiled fine. Any ideas on how to fix this issue?

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


Build a pyinstaller recipe

yasminebenghozzi6@...
 

Hello,

So have anyone been successful at making a pyinstaller recipe in yocto? Or add pyinstaller in the yocto image? 
Please I need help


[meta-tpm][PATCH v2] README: fix mailing lists and a typo

Marta Rybczynska
 

A number of typo fixes:
- tmp->tpm in the DISTRO_FEATURES
- update the mailing list address as it was out of date
- update the distro name in the subject

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-tpm/README | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta-tpm/README b/meta-tpm/README
index 4441dd2..2b32a9f 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -5,7 +5,7 @@ The bbappend files for some recipes (e.g. linux-yocto) in this layer need
to have 'tpm' in DISTRO_FEATURES to have effect.
To enable them, add in configuration file the following line.

- DISTRO_FEATURES:append = " tmp"
+ DISTRO_FEATURES:append = " tpm"

If meta-tpm is included, but tpm is not enabled as a
distro feature a warning is printed at parse time:
@@ -57,15 +57,15 @@ other layers needed. e.g.:
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-tpm][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
-$ git config format.subjectPrefix meta-security][PATCH
+$ git config sendemail.to yocto@...
+$ git config format.subjectPrefix meta-tpm][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.

--
2.30.2


[meta-tpm][PATCH] README: fix mailing lists and a typo

Marta Rybczynska
 

A number of typo fixes:
- tmp->tpm in the DISTRO_FEATURES
- update the mailing list address as it was out of date
- update the distro name in the subject

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-tpm/README | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta-tpm/README b/meta-tpm/README
index 4441dd2..5722a92 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -5,7 +5,7 @@ The bbappend files for some recipes (e.g. linux-yocto) in this layer need
to have 'tpm' in DISTRO_FEATURES to have effect.
To enable them, add in configuration file the following line.

- DISTRO_FEATURES:append = " tmp"
+ DISTRO_FEATURES:append = " tpm"

If meta-tpm is included, but tpm is not enabled as a
distro feature a warning is printed at parse time:
@@ -57,14 +57,14 @@ other layers needed. e.g.:
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
+$ git config sendemail.to yocto@...
$ git config format.subjectPrefix meta-security][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.
--
2.30.2


#linux #zeus #yocto #imx6 #bitbake #make #make #linux #zeus #yocto #imx6

noel.neu@...
 

Hi! 

I would like to implement an out-of-tree  ASoC Machine driver in my project. It #includes some in-tree header files such ../codecs/codecX.h. These are however not found when I try to build the recipe. I have followed the example project "hello-mod", but that doesn't require any in-tree header files, so it doesn't help in this case. 

What do I need to do in oder for Bitbake to find these headers ?
Thanks!


Re: oFono Version 1.31 ofonod crash

JH
 

Hi Sergei,

Thanks for the advice, the latest ofono in oe-core master is 1.32, but
I am in branch Hardknott, so I copied ofono 1.32 from master to my
layer running Hardknott branch, but I could not build ofono 1.32 in
Hardknott:

ERROR: ParseError at
/build/oe-cor/../meta-solar/recipes-connectivity/ofono/ofono_1.32.bb:22:
unparsed line: 'SYSTEMD_SERVICE:${PN} = "ofono.service"'

I used ofono 1.30 and connman 1.37 in Zeus, both worked fine , but
both connman 1.39 and ofono 1.31 failed to work properly in oe-core
Hardknott branch, to narrow down if it is ofono issue or Yocto OE
build or other library issue, I was able to build ofono 1.30 for
Hardknott, I can confirm that ofono 1.30 failed just like the 1.31
stuck at the statement add_serial_device.

................
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property

If I run ofono 1.30 built from Zeus build, the ofonod would pass
missing OFONO_DRIVER property and kept it work:

......
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem()
/sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem() driver=ubloxqmi
ofonod[3712]: ../ofono-1.30/src/modem.c:ofono_modem_create() name:
(null), type: ubloxqmi
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:setup_ubloxqmi()
/sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
.....

So I don't think it is an oFono issue, but rather an OE Yocto build or
library issue, can anyone run oFono in oe-core Hardknott branch?

Thank you.

Kind regards,

- jupiter



On 8/22/21, Sergei Golubtsov <s.e.golubtsov@...> wrote:
Hi jupiter,

Please try to update ofono to the latest release. Seems to be a library
incompatibility issue or something like that.

Yours sincerely,
Sergei Golubtsov.


On Sat, Aug 21, 2021 at 4:09 AM Jupiter <jupiter.hce@...> wrote:

Hi,

I build ofono v1.31 from git://git.yoctoproject.org/poky branch
hardknott,

$ cat meta/recipes-connectivity/ofono/ofono_1.31.bb

SUMMARY = "open source telephony"
DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
oFono supports speaking to telephony devices through specific drivers,
or with generic AT commands."
HOMEPAGE = "http://www.ofono.org"
BUGTRACKER = "https://01.org/jira/browse/OF"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \


file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"
DEPENDS = "dbus glib-2.0 udev mobile-broadband-provider-info ell"

SRC_URI = "\
${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
file://ofono \
file://0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
\
"
SRC_URI[md5sum] = "1c26340e3c6ed132cc812595081bb3dc"
SRC_URI[sha256sum] =
"a15c5d28096c10eb30e47a68b6dc2e7c4a5a99d7f4cfedf0b69624f33d859e9b"

inherit autotools pkgconfig update-rc.d systemd
gobject-introspection-data

INITSCRIPT_NAME = "ofono"
INITSCRIPT_PARAMS = "defaults 22"
SYSTEMD_SERVICE_${PN} = "ofono.service"

PACKAGECONFIG ??= "\
${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)}
\
"
PACKAGECONFIG[systemd] =
"--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, bluez5"

EXTRA_OECONF += "--enable-test --enable-external-ell"

do_install_append() {
install -d ${D}${sysconfdir}/init.d/
install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
}

PACKAGES =+ "${PN}-tests"

FILES_${PN} += "${systemd_unitdir}"
FILES_${PN}-tests = "${libdir}/${BPN}/test"

RDEPENDS_${PN} += "dbus"
RDEPENDS_${PN}-tests = "\
python3-core \
python3-dbus \
${@bb.utils.contains('GI_DATA_ENABLED', 'True',
'python3-pygobject', '', d)} \
"

RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"

The build was fine, but running the v1.31 ofono.service crashed at
udevng.c missing OFONO_DRIVER property, the ofono.service was repeated
to be restarted every 6 seconds:

.....

ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
......

I am not quite sure if it is ofono 1.31 problem or oe-core
ofono_1.31.bb problem, could anyone have a look at and advise? Let me
know if you need more debug information.

Thank you.

Kind regards,

- jupiter


On 8/20/21, Jupiter <jupiter.hce@...> wrote:
Hi,

I upgraded from Zeus to Hardknotte, I was able to run dbus to get
interface properties, but I failed on Hardknotte ofono 1.31. Has
anyone got oFono 1.31 dbus work?

Thank you.

Kind regards,

- jupiter
_______________________________________________
ofono mailing list -- ofono@...
To unsubscribe send an email to ofono-leave@...

--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


[meta-hardening][PATCH] README: fix mailing lists

Marta Rybczynska
 

The address included in the meta-hardening documentation
does not work and was changed in other places in 2019.

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-hardening/README | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-hardening/README b/meta-hardening/README
index 37a0b7e..191253c 100644
--- a/meta-hardening/README
+++ b/meta-hardening/README
@@ -64,14 +64,14 @@ layers: meta-oe
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-hardening][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-hardening][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
+$ git config sendemail.to yocto@...
$ git config format.subjectPrefix meta-hardening][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.
--
2.30.2


[meta-hardening][PATCH] meta-hardening/binutils: harden installation permissions

Marta Rybczynska
 

Compilers and related utils are better restricted on production platforms.
Change permissions of all installed binutils tools to remove access from
users outside of the root group.

This also demonstrates how to restrict file permissions in a hardened
distribution.

Signed-off-by: Marta Rybczynska <marta.rybczynska@...>
---
meta-hardening/recipes-devtools/binutils/binutils_%.bbappend | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-hardening/recipes-devtools/binutils/binutils_%.bbappend

diff --git a/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend b/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend
new file mode 100644
index 0000000..3eb3ad0
--- /dev/null
+++ b/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend
@@ -0,0 +1,3 @@
+do_install_append_class-target () {
+ chmod o-rx ${D}${prefix}/${TARGET_SYS}/bin/*
+}
--
2.30.2

2841 - 2860 of 57376