[yocto] [meta-selinux][PATCH] busybox: fix usrmerge install
If DISTRO_FEATURES contains usrmerge then busybox binaries are
installed under /usr/bin not /bin so use ${base_bindir} to support
both paths and avoid QA errors.
Signed-off-by: Ioan-Adrian Ratiu
---
recipes-core/busybox/busybox_selinux.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes-core/busybox/busybox_selinux.inc
b/recipes-core/busybox/busybox_selinux.inc
index 3f20815..c38672b 100644
--- a/recipes-core/busybox/busybox_selinux.inc
+++ b/recipes-core/busybox/busybox_selinux.inc
@@ -46,10 +46,10 @@ python create_sh_wrapper_reset_alternative_vars () {
return
if os.path.exists('%s/etc/busybox.links' % (dvar)):
-create_sh_alternative_vars("/etc/busybox.links", "/bin/busybox",
0o0755)
+create_sh_alternative_vars("/etc/busybox.links",
"${base_bindir}/busybox", 0o0755)
else:
-create_sh_alternative_vars("/etc/busybox.links.nosuid",
"/bin/busybox.nosuid", 0o0755)
-create_sh_alternative_vars("/etc/busybox.links.suid",
"/bin/busybox.suid", 0o4755)
+create_sh_alternative_vars("/etc/busybox.links.nosuid",
"${base_bindir}/busybox.nosuid", 0o0755)
+create_sh_alternative_vars("/etc/busybox.links.suid",
"${base_bindir}/busybox.suid", 0o4755)
}
# Add to PACKAGEBUILDPKGD so it could override the alternatives, which are set
in
--
2.18.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH meta-gplv2] bc: add
Add 1.06 from oe-core as bc 1.07 is GPLv3.
Signed-off-by: Ross Burton
---
recipes-extended/bc/bc_1.06.bb| 26 +
recipes-extended/bc/files/fix-segment-fault.patch | 28 +++
2 files changed, 54 insertions(+)
create mode 100644 recipes-extended/bc/bc_1.06.bb
create mode 100644 recipes-extended/bc/files/fix-segment-fault.patch
diff --git a/recipes-extended/bc/bc_1.06.bb b/recipes-extended/bc/bc_1.06.bb
new file mode 100644
index 000..d8c8a86
--- /dev/null
+++ b/recipes-extended/bc/bc_1.06.bb
@@ -0,0 +1,26 @@
+SUMMARY = "Arbitrary precision calculator language"
+HOMEPAGE = "http://www.gnu.org/software/bc/bc.html";
+
+LICENSE = "GPLv2+ & LGPLv2.1"
+LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
+file://COPYING.LIB;md5=d8045f3b8f929c1cb29a1e3fd737b499 \
+
file://bc/bcdefs.h;endline=31;md5=46dffdaf10a99728dd8ce358e45d46d8 \
+
file://dc/dc.h;endline=25;md5=2f9c558cdd80e31b4d904e48c2374328 \
+
file://lib/number.c;endline=31;md5=99434a0898abca7784acfd36b8191199"
+
+SECTION = "base"
+DEPENDS = "flex"
+PR = "r3"
+
+SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz \
+ file://fix-segment-fault.patch "
+
+SRC_URI[md5sum] = "d44b5dddebd8a7a7309aea6c36fda117"
+SRC_URI[sha256sum] =
"4ef6d9f17c3c0d92d8798e35666175ecd3d8efac4009d6457b5c99cea72c0e33"
+
+inherit autotools texinfo update-alternatives
+
+ALTERNATIVE_${PN} = "dc"
+ALTERNATIVE_PRIORITY = "100"
+
+BBCLASSEXTEND = "native"
diff --git a/recipes-extended/bc/files/fix-segment-fault.patch
b/recipes-extended/bc/files/fix-segment-fault.patch
new file mode 100644
index 000..20c0da2
--- /dev/null
+++ b/recipes-extended/bc/files/fix-segment-fault.patch
@@ -0,0 +1,28 @@
+Upstream-Status: Pending
+
+when run command such as 'echo "a = 13" | bc -l', it segmentation faults.
+This patch is from
http://www.mail-archive.com/blfs-support@linuxfromscratch.org/msg04602.html.
+
+Signed-off-by: Kai Kang
+
+--- bc-1.06/lib/number.c.orig 2003-09-26 21:14:02.0 +
bc-1.06/lib/number.c 2003-09-26 21:14:26.0 +
+@@ -34,6 +34,7 @@
+ #include
+ #include
+ #include
++#include
+ #include /* Prototypes needed for external utility routines. */
+
+ #define bc_rt_warn rt_warn
+--- bc-1.06/bc/load.c.orig 2003-09-26 21:14:14.0 +
bc-1.06/bc/load.c 2003-09-26 21:14:26.0 +
+@@ -156,7 +156,7 @@
+ long label_no;
+ long vaf_name; /* variable, array or function number. */
+ long func;
+- program_counter save_adr;
++ static program_counter save_adr;
+
+ /* Initialize. */
+ str = code;
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH v2] busybox: fix usrmerge install
If DISTRO_FEATURES contains usrmerge then busybox binaries are
installed under /usr/bin not /bin so use ${base_bindir} to support
both paths and avoid QA errors.
Signed-off-by: Ioan-Adrian Ratiu
---
recipes-core/busybox/busybox_selinux.inc | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/recipes-core/busybox/busybox_selinux.inc
b/recipes-core/busybox/busybox_selinux.inc
index 3f20815..df7c117 100644
--- a/recipes-core/busybox/busybox_selinux.inc
+++ b/recipes-core/busybox/busybox_selinux.inc
@@ -8,6 +8,7 @@ python create_sh_wrapper_reset_alternative_vars () {
dvar = d.getVar('D', True)
pn = d.getVar('PN', True)
+base_bindir = d.getVar('base_bindir', True)
def create_sh_alternative_vars(links, target, mode):
import shutil
@@ -46,10 +47,10 @@ python create_sh_wrapper_reset_alternative_vars () {
return
if os.path.exists('%s/etc/busybox.links' % (dvar)):
-create_sh_alternative_vars("/etc/busybox.links", "/bin/busybox",
0o0755)
+create_sh_alternative_vars("/etc/busybox.links", "%s/busybox" %
base_bindir, 0o0755)
else:
-create_sh_alternative_vars("/etc/busybox.links.nosuid",
"/bin/busybox.nosuid", 0o0755)
-create_sh_alternative_vars("/etc/busybox.links.suid",
"/bin/busybox.suid", 0o4755)
+create_sh_alternative_vars("/etc/busybox.links.nosuid",
"%s/busybox.nosuid" % base_bindir, 0o0755)
+create_sh_alternative_vars("/etc/busybox.links.suid",
"%s/busybox.suid" % base_bindir, 0o4755)
}
# Add to PACKAGEBUILDPKGD so it could override the alternatives, which are set
in
--
2.18.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto dev day 2018 eurpoe
Has a date/location been set? (Is it too presumptuous of me to assume there will be a Yocto Dev Day in Scotland this year?) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto dev day 2018 eurpoe
On 07/20/2018 07:09 PM, Trevor Woerner wrote: > Has a date/location been set? I believe it has. An announcement is being formulated and will be sent to the mailing lists and posted on the Yocto web site. Give it a little time as new people are getting use to the process. kind regards, Armin > > (Is it too presumptuous of me to assume there will be a Yocto Dev Day > in Scotland this year?) > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] why compile "xserver-xorg" package on wayland projects?
hi folks:
i am working on project with "DISTRO_FEATURE" set to "wayalnd", during the
compile procedure, i saw the xserver pakage was compiled, which would complain
compile error and stop the process.
i try to debug the dependciy, it seems the "weston" package bring the
xorg-server ,package in , so i try to change the default bb file of poky
poky/meta/recipes-graphics/wayland/weston_2.0.0.bb
and comment the following line
#RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
it seems work.
i dont know the reason and want to know if any elegant way to dealt with this
prolbems?
thanks for your supply.
NOTE: linux-tina: compiling from external source tree
/home/caozilong/WorkSpace/glibc/repo/lichee/linux-4.4
Currently 2 running tasks (2538 of 4483) 56%
|
|
0: linux-tina-4.4.89-r0 do_compile - 0s (pid 1550)
1: xserver-xorg-2_1.19.3-r0 do_configure - 0s (pid 1578)--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] bitbake is corrupting my files during unpacking
Hi, I'm new to openembedded and yocto. I'm using the openpli meta layers to build openembedded https://github.com/OpenPLi/openpli-oe-core Now I'm trying to build a recipe for the kernel but I encountered a strange issue, bitbake is corrupting my source files when unpacking from zip file (http link of zip file) but not when using git to get the source the files are fine and not corrupted, the downloaded zip file itself is not corrupted and If I unzip it from the sources directory(outside bitbake environment) then the resulting files are not corrupted The zip file I'm downloading https://github.com/PLi-metas/linux-amlogic/archive/amlogic-3.14-nougat.zip examples of corruption I saw : 1- /drivers/w1/slaves/Kconfig (this file is converted to a broken symlink not to a path but to the content of the file itself, see: file build/tmp/work-shared/k2pro_s905/kernel-source/drivers/w1/slaves/Kconfig build/tmp/work-shared/k2pro_s905/kernel-source/drivers/w1/slaves/Kconfig: broken symbolic link to #\012# 1-wire slaves configuration\012#\012\012menu "1-wire Slaves"\012\012config W1_SLAVE_THERM\012\011tristate "Thermal family implementation"\012\011help\012\011 Say Y here if you want to connect 1-wire thermal sensors to your\012\011 wire.\012\012config W1_SLAVE_SMEM\012\011tristate "Simple 64bit memory family implementation"\012\011help\012\011 Say Y here if you want to connect 1-wire\012\011 simple 64bit memory rom(ds2401/ds2411/ds1990*) to your wire.\012\012config W1_SLAVE_DS2408\012\011tristate "8-Channel Addressable Switch (IO Expander) 0x29 family support (DS2408)"\012\011help\012\011 Say Y here if you want to use a 1-wire\012\011 DS2408 8-Channel Addressable Switch device support\012\012config W1_SLAVE_DS2408_READBACK\012\011bool "Read-back values written to DS2408's output register"\012\011depends on W1_SLAVE_DS2408\012\011default y\012\011help\012\011 Enabling this will cause the driver to read back the values written\012\011 to the chip's output register in order to detect errors.\012\012\011 This is slower but useful when debugging chips and/or busses.\012\012config W1_SLAVE_DS2413\012\011tristate "Dual Channel Addressable Switch 0x3a family support (DS2413)"\012\011help\012\011 Say Y here if you want to use a 1-wire\012\011 DS2413 Dual Channel Addressable Switch device support\012\012config W1_SLAVE_DS2423\012\011tristate "Counter 1-wire device (DS2423)"\012\011select CRC16\012\011help\012\011 If you enable this you can read the counter values available\012\011 in the DS2423 chipset from the w1_slave file under the\012\011 sys file system.\012\012\011 Say Y here if you want to use a 1-wire\012\011 counter family device (DS2423).\012\012config W1_SLAVE_DS2431\012\011tristate "1kb EEPROM family support (DS2431)"\012\011help\012\011 Say Y here if you want to use a 1-wire\012\011 1kb EEPROM family device (DS2431)\012\012config W1_SLAVE_DS2433\012\011tristate "4kb EEPROM family support (DS2433)"\012\011help\012\011 Say Y here if you want to use a 1-wire\012\011 4kb EEPROM family device (DS2433).\012\012config W1_SLAVE_DS2433_CRC\012\011bool "Protect DS2433 data with a CRC16"\012\011depends on W1_SLAVE_DS2433\012\011select CRC16\012\011help\012\011 Say Y here to protect DS2433 data with a CRC16.\012\011 Each block has 30 bytes of data and a two byte CRC16.\012\011 Full block writes are only allowed if the CRC is valid.\012\012config W1_SLAVE_DS2760\012\011tristate "Dallas 2760 battery monitor chip (HP iPAQ & others)"\012\011depends on W1\012\011help\012\011 If you enable this you will have the DS2760 battery monitor\012\011 chip support.\012\012\011 The battery monitor chip is used in many batteries/devices\012\011 as the one who is responsible for charging/discharging/monitoring\012\011 Li+ batteries.\012\012\011 If you are unsure, say N.\012\012config W1_SLAVE_DS2780\012\011tristate "Dallas 2780 battery monitor chip"\012\011depends on W1\012\011help\012\011 If you enable this you will have the DS2780 battery monitor\012\011 chip support.\012\012\011 The battery monitor chip is used in many batteries/devices\012\011 as the one who is responsible for charging/discharging/monitoring\012\011 Li+ batteries.\012\012\011 If you are unsure, say N.\012\012config W1_SLAVE_DS2781\012\011tristate "Dallas 2781 battery monitor chip"\012\011depends on W1\012\011help\012\011 If you enable this you will have the DS2781 battery monitor\012\011 chip support.\012\012\011 The battery monitor chip is used in many batteries/devices\012\011 as the one who is responsible for charging/discharging/monitoring\012\011 Li+ batteries.\012\012\011 If you are unsure, say N.\012\012config W1_SLAVE_DS28E04\012\011tristate "4096-Bit Addressable 1-Wire EEPROM with PIO (DS28E04-100)"\012\011depends on W1\012\011select CRC16\012\011help\012\011 If you enable this you will have the DS28E04-100\012\011 chip support.\012\012\011 Say Y
