[OE-core] [PATCH] sysvinit-inittab: Make sure new shell from start_getty gets a controlling tty
Without exec, the processes from the new shell do not get a ctty: root@intel-corei7-64:~# ps -x | grep getty 755 tty1 Ss+0:00 /sbin/getty 38400 tty1 791 ?Ss 0:00 /bin/sh /bin/start_getty 115200 ttyS0 804 ?S 0:00 grep getty In particular, the openssh client fails: root@intel-corei7-64:~# ssh -v debug1: read_passphrase: can't open /dev/tty: No such device or address Host key verification failed. This patch fixes those errors. Signed-off-by: Yong, Jonathan --- meta/recipes-core/sysvinit/sysvinit-inittab/start_getty | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty b/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty index e3d052a..ab238f6 100644 --- a/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty +++ b/meta/recipes-core/sysvinit/sysvinit-inittab/start_getty @@ -1,5 +1,5 @@ #!/bin/sh if [ -c /dev/$2 ] then - /sbin/getty -L $1 $2 $3 + exec /sbin/getty -L $1 $2 $3 fi -- 2.10.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH v2 1/1] kexec-tools: Upgrade to 2.0.14
From: He Zhe Remove kexec-aarch64.patch since it has been merged upstream Remove kexec-x32.patch since it has been reverted upstream Backport patches for kdump arm64 from: https://git.linaro.org/people/takahiro.akashi/kexec-tools.git Signed-off-by: He Zhe --- ...nd-the-semantics-of-kexec_iomem_for_each_.patch | 78 ...eneralize-and-rename-get_kernel_stext_sym.patch | 194 ...0003-arm64-identify-PHYS_OFFSET-correctly.patch | 76 .../0004-arm64-kdump-identify-memory-regions.patch | 202 + ...5-arm64-kdump-add-elf-core-header-segment.patch | 191 +++ ...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 ++ .../0007-arm64-kdump-set-up-other-segments.patch | 35 ...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 +++ ...-kdump-Add-support-for-binary-image-files.patch | 52 ++ meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb| 37 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb| 44 + 11 files changed, 1159 insertions(+), 37 deletions(-) create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb diff --git a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch new file mode 100644 index 000..822f28c --- /dev/null +++ b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch @@ -0,0 +1,78 @@ +From 02eed0f8f2748fd7579f69e5373445b52b2b8754 Mon Sep 17 00:00:00 2001 +From: AKASHI Takahiro +Date: Mon, 17 Oct 2016 13:56:58 +0900 +Subject: [PATCH 1/9] kexec: exntend the semantics of kexec_iomem_for_each_line + +The current kexec_iomem_for_each_line() counts up all the lines for which +a callback function returns zero(0) or positive, and otherwise it stops +further scanning. +This behavior is incovenient in some cases. For instance, on arm64, we want +to count up "System RAM" entries, but need to skip "reserved" entries. + +So this patch extends the semantics so that we will continue to scan +succeeding entries but not count lines for which a callback function +returns positive. + +The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not +be affected by this change because +* arm + The callback function only returns -1 or 0, and the return value of + kexec_iomem_for_each_line() will never be used. +* sh, x86 + The callback function may return (-1 for sh,) 0 or 1, but always returns + 1 once we have reached the maximum number of entries allowed. + Even so the current kexec_iomem_for_each_line() counts them up. + This change actually fixes this bug. + +Upstream-Status: Backport [https://git.linaro.org/people/takahiro.akashi/kexec-tools.git] + +Signed-off-by: AKASHI Takahiro +Signed-off-by: He Zhe +--- + kexec/kexec-iomem.c | 15 ++- + 1 file changed, 10 insertions(+), 5 deletions(-) + +diff --git a/kexec/kexec-iomem.c b/kexec/kexec-iomem.c +index 485a2e8..0a0277a 100644 +--- a/kexec/kexec-iomem.c b/kexec/kexec-iomem.c +@@ -18,6 +18,9 @@ + * Iterate over each line in the file returned by proc_iomem(). If match is + * NULL or if the line matches with our match-pattern then call the + * callback if non-NULL. ++ * If match is NULL, callback should return a negative if error. ++ * Otherwise the interation goes on, incrementing nr but only if callback ++ * returns 0 (matched). + * + * Return the number of lines matched. + */ +@@ -37,7 +40,7 @@ int kexec_iomem_for_each_line(char *match, + char *str; + int consumed; + int count; +- int nr = 0; ++ int nr = 0, ret; + + fp = fopen(iomem, "r"); + if (!fp) +@@ -50,11 +53,13 @@ int kexec_iomem_for_each_line(char *match, + str = line + consumed; +
[OE-core] [PATCH v2 0/1] kexec-tools: Upgrade to 2.0.14
From: He Zhe Remove kexec-aarch64.patch since it has been merged upstream Remove kexec-x32.patch since it has been reverted upstream Backport patches for kdump arm64 from: https://git.linaro.org/people/takahiro.akashi/kexec-tools.git v1 to v2: Remove redundant tarball link in SRC_URI He Zhe (1): kexec-tools: Upgrade to 2.0.14 ...nd-the-semantics-of-kexec_iomem_for_each_.patch | 78 ...eneralize-and-rename-get_kernel_stext_sym.patch | 194 ...0003-arm64-identify-PHYS_OFFSET-correctly.patch | 76 .../0004-arm64-kdump-identify-memory-regions.patch | 202 + ...5-arm64-kdump-add-elf-core-header-segment.patch | 191 +++ ...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 ++ .../0007-arm64-kdump-set-up-other-segments.patch | 35 ...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 +++ ...-kdump-Add-support-for-binary-image-files.patch | 52 ++ meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb| 37 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb| 44 + 11 files changed, 1159 insertions(+), 37 deletions(-) create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch create mode 100644 meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb -- 2.8.3 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
Hello Richard, bitbake | cat shows that when this logout happened during build, log file captured below packages in process: NOTE: Running task 1886 of 4212 (/home/builder/poky/meta/recipes-graphics/xorg-proto/kbproto_1.0.7.bb: do_packagedata) NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Started NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Succeeded NOTE: Running task 1887 of 4212 (/home/builder/poky/meta/recipes-support/libffi/libffi_3.2.1.bb:do_package) NOTE: recipe ncurses-6.0+20160625-r0: task do_package: Started NOTE: recipe libffi-3.2.1-r0: task do_package: Started NOTE: recipe libffi-3.2.1-r0: task do_package: Succeeded NOTE: Running task 1888 of 4212 (/home/builder/poky/meta/recipes-support/libffi/libffi_3.2.1.bb: do_packagedata) NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Started NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Succeeded NOTE: Running task 1889 of 4212 (/home/builder/poky/meta/recipes-extended/bzip2/bzip2_1.0.6.bb:do_package) NOTE: recipe bzip2-1.0.6-r5: task do_package: Started --- Also there was a crash file generated in "/var/crash" folder: /var/crash/_usr_lib_accountsservice_accounts-daemon.0.crash That has following information in it: - ProblemType: Crash Architecture: amd64 Date: Mon Dec 26 18:23:22 2016 DistroRelease: Ubuntu 14.04 ExecutablePath: /usr/lib/accountsservice/accounts-daemon ExecutableTimestamp: 1478200365 ProcCmdline: /usr/lib/accountsservice/accounts-daemon ProcCwd: / ProcEnviron: ProcMaps: 0040-00426000 r-xp 08:01 2626520 /usr/lib/accountsservice/accounts-daemon 00625000-00628000 r--p 00025000 08:01 2626520 /usr/lib/accountsservice/accounts-daemon 00628000-00629000 rw-p 00028000 08:01 2626520 /usr/lib/accountsservice/accounts-daemon 024aa000-0252a000 rw-p 00:00 0 [heap] 7fe46000-7fe460022000 rw-p 00:00 0 7fe460022000-7fe46400 ---p 00:00 0 7fe46400-7fe464021000 rw-p 00:00 0 7fe464021000-7fe46800 ---p 00:00 0 7fe469f56000-7fe469f6 r-xp 08:01 1839849 /lib/x86_64-linux-gnu/libnss_files-2.19.so 7fe469f6-7fe46a15f000 ---p a000 08:01 1839849 /lib/x86_64-linux-gnu/libnss_files-2.19.so 7fe46a15f000-7fe46a16 r--p 9000 08:01 1839849 /lib/x86_64-linux-gnu/libnss_files-2.19.so ... ... 7fe474b3e000-7fe474b4 rw-p 00:00 0 7fe474b4-7fe474b41000 r--p 00022000 08:01 1839750 /lib/x86_64-linux-gnu/ld-2.19.so 7fe474b41000-7fe474b42000 rw-p 00023000 08:01 1839750 /lib/x86_64-linux-gnu/ld-2.19.so 7fe474b42000-7fe474b43000 rw-p 00:00 0 7ffcaca64000-7ffcaca85000 rw-p 00:00 0 [stack] 7ffcacaf5000-7ffcacaf7000 r--p 00:00 0 [vvar] 7ffcacaf7000-7ffcacaf9000 r-xp 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] ProcStatus: Name: accounts-daemon State: D (disk sleep) Tgid: 1248 Ngid: 0 Pid: 1248 PPid: 1 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize:64 Groups:0 NStgid:1248 NSpid: 1248 NSpgid:795 NSsid: 795 VmPeak: 302404 kB VmSize: 302368 kB VmPin:0 kB VmHWM:10128 kB VmRSS: 4464 kB VmData: 221944 kB VmStk: 136 kB VmExe: 152 kB VmLib:10140 kB VmPTE: 200 kB VmPMD: 12 kB VmSwap:2976 kB HugetlbPages: 0 kB Threads: 3 SigQ: 0/31670 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:000180004002 CapInh: CapPrm:003f CapEff:003f CapBnd:003f CapAmb: Seccomp: 0 Cpus_allowed: ff Cpus_allowed_list: 0-7 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 152 nonvoluntary_ctxt_switches:2 Signal: 7 Uname: Linux 4.4.0-57-generic x86_64 UserGroups: CoreDump: base64 - My machine is: *Quad-Core:* (0-8) --- $ cat /proc/cpuinfo processor: 0 vendor_id: GenuineIntel cpu family: 6 model: 42 model name: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz - $ cat /proc/meminfo MemTotal:8132472 kB When I checked free memory just before the logout was about "125MB" out of 8GB RAM. NOTE: The Ubuntu-14.04.4 that had older graphics stack seem to work normally without any issue. The "ubuntu-14.04.5" & "16.04" came with latest graphics stack & ker
Re: [OE-core] Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
Hello Richard, Sure, watching is best thing we can do, but it happens somewhere after 2900 tasks i.e just after linux-yocto. Screen recorders usually ask for file name and destination folder for saving the file, will try to see if it works as you said. "bitbake | cat" is the best method that we can get info from. The issue is noticeable only in ubuntu (unity) desktop's and not in Kubuntu (KDE), Ubuntu-gnome (Gnome-3) or Xubuntu (XFCE) desktops. Will fetch more details as per your suggestion. Thank you ! On Mon, Dec 26, 2016 at 4:06 PM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote: > > Environment: Ubuntu-14.04.5/16.04.1 (64-bit) > > Yocto build: qemuarm > > Target image: core-image-sato > > Error nature: The lightdm restarts on its own and logs out by killing > > processes running and brings up a login UI. > > > > > > We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and > > Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop > > Manager) that is triggered by crash of "unity-settings-daemon", we > > couldn't figure out any workaround so far to overcome the issue. The > > build goes fine in the beginning but eventually the unity desktop > > logs out and kills all the processes running in the user session > > (including bitbake) and lands us into "Login screen" and when we > > login its a new session where as the bitbake running in previous > > session is killed and we need to continue the build. This is > > happening consistently when the user logs into desktop via lightdm > > and triggers a build. > > > > Another interesting thing to notice is the build goes fine if we > > connect to host via. SSH session and invoke a bitbake build. We are > > suspecting on unity-settings-daemon that is crashing consistently and > > is evident from the ".xsession-errors" log file as shown below: > > > > builder@ubuntu:~$ cat .xsession-errors.old > > Script for ibus started at run_im. > > Script for auto started at run_im. > > Script for default started at run_im. > > init: Disconnected from notified D-Bus bus > > init:"unity-settings-daemon main process (2076) terminated with > > status 1" > > init: indicator-bluetooth main process (2212) killed by TERM signal > > init: indicator-power main process (2214) killed by TERM signal > > init: indicator-datetime main process (2215) killed by TERM signal > > init: indicator-printers main process () killed by TERM signal > > init: indicator-session main process (2245) killed by TERM signal > > init: indicator-application main process (2270) killed by TERM signal > > > > Corresponding unity-settings-daemon bug reported in Launchpad: > > > > https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/ > > 1546641 > > > > Would anyone kindly confirm the logout behaviour during bitbake > > process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions > > both Ubuntu-14.04 & 16.04 as supported distributions this blocker > > issue must be resolved at earliest. > > > > Appreciate your Inputs ! > > What would really help is knowing what recipe is being built when this > happens. There are a few ways you might be able to figure this out: > > a) Watching the screen to see which recipes were building when it > happens > b) Perhaps using some kind of screen recorder to automate this, you'd > be able to review the recording to see when it breaks > c) Looking at the bitbake/build logs to see what it was doing when the > build broke (assuming bitbake stops when the session dies). > > "bitbake | cat" can provide better output for this since it will > produce a scrolling log rather than the more interactive UI. > > Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake > XXX" should hopefully reproduce this more easily. > > Cheers, > > Richard > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote: > Environment: Ubuntu-14.04.5/16.04.1 (64-bit) > Yocto build: qemuarm > Target image: core-image-sato > Error nature: The lightdm restarts on its own and logs out by killing > processes running and brings up a login UI. > > > We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and > Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop > Manager) that is triggered by crash of "unity-settings-daemon", we > couldn't figure out any workaround so far to overcome the issue. The > build goes fine in the beginning but eventually the unity desktop > logs out and kills all the processes running in the user session > (including bitbake) and lands us into "Login screen" and when we > login its a new session where as the bitbake running in previous > session is killed and we need to continue the build. This is > happening consistently when the user logs into desktop via lightdm > and triggers a build. > > Another interesting thing to notice is the build goes fine if we > connect to host via. SSH session and invoke a bitbake build. We are > suspecting on unity-settings-daemon that is crashing consistently and > is evident from the ".xsession-errors" log file as shown below: > > builder@ubuntu:~$ cat .xsession-errors.old > Script for ibus started at run_im. > Script for auto started at run_im. > Script for default started at run_im. > init: Disconnected from notified D-Bus bus > init:"unity-settings-daemon main process (2076) terminated with > status 1" > init: indicator-bluetooth main process (2212) killed by TERM signal > init: indicator-power main process (2214) killed by TERM signal > init: indicator-datetime main process (2215) killed by TERM signal > init: indicator-printers main process () killed by TERM signal > init: indicator-session main process (2245) killed by TERM signal > init: indicator-application main process (2270) killed by TERM signal > > Corresponding unity-settings-daemon bug reported in Launchpad: > > https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/ > 1546641 > > Would anyone kindly confirm the logout behaviour during bitbake > process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions > both Ubuntu-14.04 & 16.04 as supported distributions this blocker > issue must be resolved at earliest. > > Appreciate your Inputs ! What would really help is knowing what recipe is being built when this happens. There are a few ways you might be able to figure this out: a) Watching the screen to see which recipes were building when it happens b) Perhaps using some kind of screen recorder to automate this, you'd be able to review the recording to see when it breaks c) Looking at the bitbake/build logs to see what it was doing when the build broke (assuming bitbake stops when the session dies). "bitbake | cat" can provide better output for this since it will produce a scrolling log rather than the more interactive UI. Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake XXX" should hopefully reproduce this more easily. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm
Hello, Environment: Ubuntu-14.04.5/16.04.1 (64-bit) Yocto build: qemuarm Target image: core-image-sato Error nature: The lightdm restarts on its own and logs out by killing processes running and brings up a login UI. We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop Manager) that is triggered by crash of "unity-settings-daemon", we couldn't figure out any workaround so far to overcome the issue. The build goes fine in the beginning but eventually the unity desktop logs out and kills all the processes running in the user session (including bitbake) and lands us into "Login screen" and when we login its a new session where as the bitbake running in previous session is killed and we need to continue the build. This is happening consistently when the user logs into desktop via lightdm and triggers a build. Another interesting thing to notice is the build goes fine if we connect to host via. SSH session and invoke a bitbake build. We are suspecting on unity-settings-daemon that is crashing consistently and is evident from the ".xsession-errors" log file as shown below: builder@ubuntu:~$ cat .xsession-errors.old Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: Disconnected from notified D-Bus bus init:"unity-settings-daemon main process (2076) terminated with status 1" init: indicator-bluetooth main process (2212) killed by TERM signal init: indicator-power main process (2214) killed by TERM signal init: indicator-datetime main process (2215) killed by TERM signal init: indicator-printers main process () killed by TERM signal init: indicator-session main process (2245) killed by TERM signal init: indicator-application main process (2270) killed by TERM signal Corresponding unity-settings-daemon bug reported in Launchpad: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641 Would anyone kindly confirm the logout behaviour during bitbake process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions both Ubuntu-14.04 & 16.04 as supported distributions this blocker issue must be resolved at earliest. Appreciate your Inputs ! Thanks in Advance. -Srikant -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 7/7] coreutils: upgrade to 8.26
Add 0001-local.mk-fix-cross-compiling-problem.patch to fix the following
cross compiling problem.
| Makefile:3418: *** Recursive variable 'INSTALL' references itself
(eventually). Stop.
Signed-off-by: Chen Qi
---
...need_charset_alias-when-building-for-musl.patch | 0
...0001-local.mk-fix-cross-compiling-problem.patch | 26 ++
...e-report-processor-and-hardware-correctly.patch | 0
.../disable-ls-output-quoting.patch| 0
.../fix-selinux-flask.patch| 0
.../man-decouple-manpages-from-build.patch | 0
.../remove-usr-local-lib-from-m4.patch | 0
.../{coreutils_8.25.bb => coreutils_8.26.bb} | 9
8 files changed, 31 insertions(+), 4 deletions(-)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/0001-Unset-need_charset_alias-when-building-for-musl.patch
(100%)
create mode 100644
meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/0001-uname-report-processor-and-hardware-correctly.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/disable-ls-output-quoting.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/fix-selinux-flask.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/man-decouple-manpages-from-build.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/remove-usr-local-lib-from-m4.patch (100%)
rename meta/recipes-core/coreutils/{coreutils_8.25.bb => coreutils_8.26.bb}
(93%)
diff --git
a/meta/recipes-core/coreutils/coreutils-8.25/0001-Unset-need_charset_alias-when-building-for-musl.patch
b/meta/recipes-core/coreutils/coreutils-8.26/0001-Unset-need_charset_alias-when-building-for-musl.patch
similarity index 100%
rename from
meta/recipes-core/coreutils/coreutils-8.25/0001-Unset-need_charset_alias-when-building-for-musl.patch
rename to
meta/recipes-core/coreutils/coreutils-8.26/0001-Unset-need_charset_alias-when-building-for-musl.patch
diff --git
a/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
b/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
new file mode 100644
index 000..66f9a71
--- /dev/null
+++
b/meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
@@ -0,0 +1,26 @@
+Subject: local.mk: fix cross compiling problem
+
+We meet the following error when cross compiling.
+| Makefile:3418: *** Recursive variable 'INSTALL' references itself
(eventually). Stop.
+This patch fixes this problem.
+
+Upstream-Status: Pending
+
+Signed-off-by: Chen Qi
+---
+ src/local.mk | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/local.mk b/src/local.mk
+index 36dfa4e..c5898cc 100644
+--- a/src/local.mk
b/src/local.mk
+@@ -649,4 +649,4 @@ cu_install_program = @INSTALL_PROGRAM@
+ else
+ cu_install_program = src/ginstall
+ endif
+-INSTALL = $(cu_install_program) -c
++INSTALL_PROGRAM = $(cu_install_program)
+--
+2.1.0
+
diff --git
a/meta/recipes-core/coreutils/coreutils-8.25/0001-uname-report-processor-and-hardware-correctly.patch
b/meta/recipes-core/coreutils/coreutils-8.26/0001-uname-report-processor-and-hardware-correctly.patch
similarity index 100%
rename from
meta/recipes-core/coreutils/coreutils-8.25/0001-uname-report-processor-and-hardware-correctly.patch
rename to
meta/recipes-core/coreutils/coreutils-8.26/0001-uname-report-processor-and-hardware-correctly.patch
diff --git
a/meta/recipes-core/coreutils/coreutils-8.25/disable-ls-output-quoting.patch
b/meta/recipes-core/coreutils/coreutils-8.26/disable-ls-output-quoting.patch
similarity index 100%
rename from
meta/recipes-core/coreutils/coreutils-8.25/disable-ls-output-quoting.patch
rename to
meta/recipes-core/coreutils/coreutils-8.26/disable-ls-output-quoting.patch
diff --git a/meta/recipes-core/coreutils/coreutils-8.25/fix-selinux-flask.patch
b/meta/recipes-core/coreutils/coreutils-8.26/fix-selinux-flask.patch
similarity index 100%
rename from meta/recipes-core/coreutils/coreutils-8.25/fix-selinux-flask.patch
rename to meta/recipes-core/coreutils/coreutils-8.26/fix-selinux-flask.patch
diff --git
a/meta/recipes-core/coreutils/coreutils-8.25/man-decouple-manpages-from-build.patch
b/meta/recipes-core/coreutils/coreutils-8.26/man-decouple-manpages-from-build.patch
similarity index 100%
rename from
meta/recipes-core/coreutils/coreutils-8.25/man-decouple-manpages-from-build.patch
rename to
meta/recipes-core/coreutils/coreutils-8.26/man-decouple-manpages-from-build.patch
diff --git
a/meta/recipes-core/coreutils/coreutils-8.25/remove-usr-local-lib-from-m4.patch
b/meta/recipes-core/coreutils/coreutils-8.26/remove-usr-local-lib-from-m4.patch
similarity index 100%
rename from
meta/recipes-core/coreutils/coreutils-8.25/remove-u
[OE-core] [PATCH 5/7] grep: upgrade to 2.27
Signed-off-by: Chen Qi
---
meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} (88%)
diff --git a/meta/recipes-extended/grep/grep_2.26.bb
b/meta/recipes-extended/grep/grep_2.27.bb
similarity index 88%
rename from meta/recipes-extended/grep/grep_2.26.bb
rename to meta/recipes-extended/grep/grep_2.27.bb
index 9e6f05e..7d0a73b 100644
--- a/meta/recipes-extended/grep/grep_2.26.bb
+++ b/meta/recipes-extended/grep/grep_2.27.bb
@@ -9,8 +9,8 @@ SRC_URI = "${GNU_MIRROR}/grep/grep-${PV}.tar.xz \
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
"
-SRC_URI[md5sum] = "afdd61c7221434722671baf002ac9267"
-SRC_URI[sha256sum] =
"246a8fb37e82aa33d495b07c22fdab994c039ab0f818538eac81b01e78636870"
+SRC_URI[md5sum] = "6138dd227c39d4a25f81eea76a44d4cb"
+SRC_URI[sha256sum] =
"ad4cc44d23074a1c3a8baae8fbafff2a8c60f38a9a6108f985eef6fbee6dcaeb"
inherit autotools gettext texinfo
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 6/7] byacc: upgrade to 20161202
Signed-off-by: Chen Qi
---
meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb}
(74%)
diff --git a/meta/recipes-extended/byacc/byacc_20160606.bb
b/meta/recipes-extended/byacc/byacc_20161202.bb
similarity index 74%
rename from meta/recipes-extended/byacc/byacc_20160606.bb
rename to meta/recipes-extended/byacc/byacc_20161202.bb
index 98129d0..755f8ab 100644
--- a/meta/recipes-extended/byacc/byacc_20160606.bb
+++ b/meta/recipes-extended/byacc/byacc_20161202.bb
@@ -8,5 +8,5 @@ LIC_FILES_CHKSUM =
"file://package/debian/copyright;md5=74533d32ffd38bca4cbf1f13
require byacc.inc
-SRC_URI[md5sum] = "d527c811b360f04a8c5f5a0a90625966"
-SRC_URI[sha256sum] =
"cc8fdced486cb70cec7a7c9358de836bfd267d19d6456760bb4721ccfea5ac91"
+SRC_URI[md5sum] = "48ef38447f2cc864c70ef864b26cf817"
+SRC_URI[sha256sum] =
"30dc58cfcdb708eea7ba022db29b41d2d392f20727491b956954366f2f2117f0"
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/7] systemd-bootchart: upgrade to 231
Signed-off-by: Chen Qi
---
.../{systemd-bootchart_230.bb => systemd-bootchart_231.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/systemd-bootchart/{systemd-bootchart_230.bb =>
systemd-bootchart_231.bb} (92%)
diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
similarity index 92%
rename from meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
rename to meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
index 9ce629a..1d88036 100644
--- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
+++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb
@@ -5,8 +5,8 @@ LIC_FILES_CHKSUM =
"file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c
SRC_URI = "git://github.com/systemd/systemd-bootchart.git;protocol=https"
# Modify these as desired
-PV = "230+git${SRCPV}"
-SRCREV = "dcb246b46239259ec99b3c6e6ab7d27e1a5a8a84"
+PV = "231+git${SRCPV}"
+SRCREV = "9ee2ffc1dc6c8209725e625954bbd89f96cb7139"
S = "${WORKDIR}/git"
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 4/7] flex: upgrade to 2.6.2
Upgrade flex to 2.6.2.
The following two patches are removed as they have been merged.
0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
CVE-2016-6354.patch
do_not_create_pdf_doc.patch is removed as it's not suitable for the new
version.
0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch is added
to fix cross compiling problem.
Signed-off-by: Chen Qi
---
...lex-from-flex-native-to-fix-cross-compili.patch | 51 +
...oid-c-comments-in-c-code-fails-with-gcc-6.patch | 64 --
.../recipes-devtools/flex/flex/CVE-2016-6354.patch | 59
.../flex/flex/do_not_create_pdf_doc.patch | 17 --
.../flex/{flex_2.6.0.bb => flex_2.6.2.bb} | 16 +++---
5 files changed, 60 insertions(+), 147 deletions(-)
create mode 100644
meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
delete mode 100644
meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
delete mode 100644 meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
delete mode 100644 meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
rename meta/recipes-devtools/flex/{flex_2.6.0.bb => flex_2.6.2.bb} (79%)
diff --git
a/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
b/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
new file mode 100644
index 000..08f7688
--- /dev/null
+++
b/meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
@@ -0,0 +1,51 @@
+Subject: use stage1flex from flex-native to fix cross compiling
+
+When cross compiling, we would have failure because stage1flex cannot run on
host.
+Use stage1flex from flex-native to fix this problem.
+
+This patch is OE specific as upstream may have other way to fix this cross
compilation
+problem.
+
+Upstream-Status: Inappropriate [OE specific]
+
+Signed-off-by: Chen Qi
+---
+ src/Makefile.am | 11 ++-
+ 1 file changed, 2 insertions(+), 9 deletions(-)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 77ddf4b..09ffddb 100644
+--- a/src/Makefile.am
b/src/Makefile.am
+@@ -6,17 +6,10 @@ LIBS = @LIBS@
+ m4 = @M4@
+
+ bin_PROGRAMS = flex
+-noinst_PROGRAMS = stage1flex
+ lib_LTLIBRARIES = \
+ libfl.la \
+ libfl_pic.la
+
+-stage1flex_SOURCES = \
+- scan.l \
+- $(COMMON_SOURCES)
+-
+-stage1flex_CFLAGS = $(AM_CFLAGS)
+-
+ flex_SOURCES = \
+ $(COMMON_SOURCES)
+
+@@ -89,8 +82,8 @@ skel.c: flex.skl mkskel.sh flexint.h tables_shared.h
tables_shared.c
+ $(SHELL) $(srcdir)/mkskel.sh > $@.tmp
+ mv $@.tmp $@
+
+-stage1scan.c: scan.l stage1flex$(EXEEXT)
+- ./stage1flex$(EXEEXT) -o $@ $<
++stage1scan.c: scan.l
++ stage1flex$(EXEEXT) -o $@ $<
+
+ # make needs to be told to make parse.h so that parallelized runs will
+ # not fail.
+--
+2.1.0
+
diff --git
a/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
b/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
deleted file mode 100644
index 438ca5f..000
---
a/meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
+++ /dev/null
@@ -1,64 +0,0 @@
-From 7072befe1397af4eb01c3ff7edf99f0cd5076089 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Andreas=20M=C3=BCller?=
-Date: Tue, 30 Aug 2016 14:25:32 +0200
-Subject: [PATCH] avoid c++ comments in c-code - fails with gcc-6
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-fixes:
-
-| error: C++ style comments are not allowed in ISO C90
-| num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
-
-Upstream-Status: Pending
-
-Signed-off-by: Andreas Müller
- src/flex.skl | 2 +-
- src/scan.c | 2 +-
- src/skel.c | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/src/flex.skl b/src/flex.skl
-index 73a0b9e..ed71627 100644
a/src/flex.skl
-+++ b/src/flex.skl
-@@ -2350,7 +2350,7 @@ void yyFlexLexer::yyensure_buffer_stack(void)
-* scanner will even need a stack. We use 2 instead of 1 to
avoid an
-* immediate realloc on the next call.
- */
-- num_to_alloc = 1; // After all that talk, this was set to 1
anyways...
-+ num_to_alloc = 1; /* After all that talk, this was set to 1
anyways... */
- YY_G(yy_buffer_stack) = (struct yy_buffer_state**)yyalloc
- (num_to_alloc *
sizeof(struct yy_buffer_state*)
-
M4_YY_CALL_LAST_ARG);
-diff --git a/src/scan.c b/src/scan.c
-index b55df2d..f1dce75 100644
a/src/scan.c
-+++ b/src/scan.c
-@@ -4672,7 +4672,7 @@ static void yyensure_buffer_stack (void)
-* scanner will even need a stack. We use 2 instead
[OE-core] [PATCH 2/7] dbus/dbus-test: upgrade to 1.10.14
Signed-off-by: Chen Qi
---
meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} | 4 ++--
meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb}
(93%)
rename meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} (98%)
diff --git a/meta/recipes-core/dbus/dbus-test_1.10.10.bb
b/meta/recipes-core/dbus/dbus-test_1.10.14.bb
similarity index 93%
rename from meta/recipes-core/dbus/dbus-test_1.10.10.bb
rename to meta/recipes-core/dbus/dbus-test_1.10.14.bb
index 650b7ab..5394814 100644
--- a/meta/recipes-core/dbus/dbus-test_1.10.10.bb
+++ b/meta/recipes-core/dbus/dbus-test_1.10.14.bb
@@ -17,8 +17,8 @@ SRC_URI =
"http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://clear-guid_from_server-if-send_negotiate_unix_f.patch \
"
-SRC_URI[md5sum] = "495676d240eb982921b3ad1343526849"
-SRC_URI[sha256sum] =
"9d8f1d069ab4d1a0255d7b400ea3bcef4430c42e729b1012abb2890e3f739a43"
+SRC_URI[md5sum] = "3f7b013ce8f641cd4c897acda0ef3467"
+SRC_URI[sha256sum] =
"23238f70353e38ce5ca183ebc9525c0d97ac00ef640ad29cf794782af6e6a083"
S="${WORKDIR}/dbus-${PV}"
FILESEXTRAPATHS =. "${FILE_DIRNAME}/dbus:"
diff --git a/meta/recipes-core/dbus/dbus_1.10.10.bb
b/meta/recipes-core/dbus/dbus_1.10.14.bb
similarity index 98%
rename from meta/recipes-core/dbus/dbus_1.10.10.bb
rename to meta/recipes-core/dbus/dbus_1.10.14.bb
index 4db0b9b..2ffd8b0 100644
--- a/meta/recipes-core/dbus/dbus_1.10.10.bb
+++ b/meta/recipes-core/dbus/dbus_1.10.14.bb
@@ -20,8 +20,8 @@ SRC_URI =
"http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://0001-configure.ac-explicitely-check-stdint.h.patch \
"
-SRC_URI[md5sum] = "495676d240eb982921b3ad1343526849"
-SRC_URI[sha256sum] =
"9d8f1d069ab4d1a0255d7b400ea3bcef4430c42e729b1012abb2890e3f739a43"
+SRC_URI[md5sum] = "3f7b013ce8f641cd4c897acda0ef3467"
+SRC_URI[sha256sum] =
"23238f70353e38ce5ca183ebc9525c0d97ac00ef640ad29cf794782af6e6a083"
inherit useradd autotools pkgconfig gettext update-rc.d
upstream-version-is-even
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/7] sysstat: upgrade to 11.5.3
Signed-off-by: Chen Qi
---
.../recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb}
(53%)
diff --git a/meta/recipes-extended/sysstat/sysstat_11.4.0.bb
b/meta/recipes-extended/sysstat/sysstat_11.5.3.bb
similarity index 53%
rename from meta/recipes-extended/sysstat/sysstat_11.4.0.bb
rename to meta/recipes-extended/sysstat/sysstat_11.5.3.bb
index 69f83fc..bb6a671 100644
--- a/meta/recipes-extended/sysstat/sysstat_11.4.0.bb
+++ b/meta/recipes-extended/sysstat/sysstat_11.5.3.bb
@@ -4,5 +4,5 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=a23a74b3f4caf9616230789d94217acb"
SRC_URI += "file://0001-Include-needed-headers-explicitly.patch"
-SRC_URI[md5sum] = "ee7b8c0b139a11a7a3418dc0658ca1be"
-SRC_URI[sha256sum] =
"b8518ca88acfcbc474a406022ee9c0c3210ccef4f0ec80e5b3e8c41dda8c16f2"
+SRC_URI[md5sum] = "5986da64af934d8cecc7bca7ebe43752"
+SRC_URI[sha256sum] =
"f8229d14819e2d461ede83894648e03c8a2ad14a1ba200d68cda9816c42f41ea"
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/7] Package Upgrade: systemd-bootchart, dbus, dus-test, sysstat, flex, grep, byacc, coreutils
The following changes since commit dbb247cac5fbf7b037e4955f9793828451723924:
bitbake: cookerdata: Convert multiconfig to use BB_CURRENT_MC (2016-12-22
12:36:40 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/PU-20161226
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/PU-20161226
Chen Qi (7):
systemd-bootchart: upgrade to 231
dbus/dbus-test: upgrade to 1.10.14
sysstat: upgrade to 11.5.3
flex: upgrade to 2.6.2
grep: upgrade to 2.27
byacc: upgrade to 20161202
coreutils: upgrade to 8.26
...need_charset_alias-when-building-for-musl.patch | 0
...0001-local.mk-fix-cross-compiling-problem.patch | 26 +
...e-report-processor-and-hardware-correctly.patch | 0
.../disable-ls-output-quoting.patch| 0
.../fix-selinux-flask.patch| 0
.../man-decouple-manpages-from-build.patch | 0
.../remove-usr-local-lib-from-m4.patch | 0
.../{coreutils_8.25.bb => coreutils_8.26.bb} | 9 +--
.../{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb} | 4 +-
.../dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} | 4 +-
...lex-from-flex-native-to-fix-cross-compili.patch | 51 +
...oid-c-comments-in-c-code-fails-with-gcc-6.patch | 64 --
.../recipes-devtools/flex/flex/CVE-2016-6354.patch | 59
.../flex/flex/do_not_create_pdf_doc.patch | 17 --
.../flex/{flex_2.6.0.bb => flex_2.6.2.bb} | 16 +++---
...d-bootchart_230.bb => systemd-bootchart_231.bb} | 4 +-
.../byacc/{byacc_20160606.bb => byacc_20161202.bb} | 4 +-
.../grep/{grep_2.26.bb => grep_2.27.bb}| 4 +-
.../{sysstat_11.4.0.bb => sysstat_11.5.3.bb} | 4 +-
19 files changed, 103 insertions(+), 163 deletions(-)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/0001-Unset-need_charset_alias-when-building-for-musl.patch
(100%)
create mode 100644
meta/recipes-core/coreutils/coreutils-8.26/0001-local.mk-fix-cross-compiling-problem.patch
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/0001-uname-report-processor-and-hardware-correctly.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/disable-ls-output-quoting.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/fix-selinux-flask.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/man-decouple-manpages-from-build.patch (100%)
rename meta/recipes-core/coreutils/{coreutils-8.25 =>
coreutils-8.26}/remove-usr-local-lib-from-m4.patch (100%)
rename meta/recipes-core/coreutils/{coreutils_8.25.bb => coreutils_8.26.bb}
(93%)
rename meta/recipes-core/dbus/{dbus-test_1.10.10.bb => dbus-test_1.10.14.bb}
(93%)
rename meta/recipes-core/dbus/{dbus_1.10.10.bb => dbus_1.10.14.bb} (98%)
create mode 100644
meta/recipes-devtools/flex/flex/0001-use-stage1flex-from-flex-native-to-fix-cross-compili.patch
delete mode 100644
meta/recipes-devtools/flex/flex/0002-avoid-c-comments-in-c-code-fails-with-gcc-6.patch
delete mode 100644 meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
delete mode 100644 meta/recipes-devtools/flex/flex/do_not_create_pdf_doc.patch
rename meta/recipes-devtools/flex/{flex_2.6.0.bb => flex_2.6.2.bb} (79%)
rename meta/recipes-devtools/systemd-bootchart/{systemd-bootchart_230.bb =>
systemd-bootchart_231.bb} (92%)
rename meta/recipes-extended/byacc/{byacc_20160606.bb => byacc_20161202.bb}
(74%)
rename meta/recipes-extended/grep/{grep_2.26.bb => grep_2.27.bb} (88%)
rename meta/recipes-extended/sysstat/{sysstat_11.4.0.bb => sysstat_11.5.3.bb}
(53%)
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
