Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Serhey Popovych <serhe.popovych@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] systemd: Use arch overrides instead of machine
Date: Sat, 12 Jan 2019 11:22:48 +0200	[thread overview]
Message-ID: <1547284970-20783-3-git-send-email-serhe.popovych@gmail.com> (raw)
In-Reply-To: <1547284970-20783-1-git-send-email-serhe.popovych@gmail.com>

With custom BSP and build with musl we still affected by undefined
reference to stack-protector specific functions.

Use arch overrides instead of machine to ensure fix applied to entire
architecture instead of custom machine like qemux86 and qemuppc.

Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com>
---
 meta/recipes-core/systemd/systemd_239.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_239.bb b/meta/recipes-core/systemd/systemd_239.bb
index 0f1fa27..2e11d71 100644
--- a/meta/recipes-core/systemd/systemd_239.bb
+++ b/meta/recipes-core/systemd/systemd_239.bb
@@ -66,9 +66,9 @@ SRC_URI_MUSL = "file://0001-Use-getenv-when-secure-versions-are-not-available.pa
                file://0022-Use-if-instead-of-ifdef-for-ENABLE_GSHADOW.patch \
                "
 
-# Workaround undefined reference to `__stack_chk_fail_local' on qemux86 and qemuppc for musl
-SRC_URI_append_libc-musl_qemux86 = " file://0001-Remove-fstack-protector-flags-to-workaround-musl-bui.patch"
-SRC_URI_append_libc-musl_qemuppc = " file://0001-Remove-fstack-protector-flags-to-workaround-musl-bui.patch"
+# Workaround undefined reference to `__stack_chk_fail_local' on x86 and powerpc for musl
+SRC_URI_append_libc-musl_x86 = " file://0001-Remove-fstack-protector-flags-to-workaround-musl-bui.patch"
+SRC_URI_append_libc-musl_powerpc = " file://0001-Remove-fstack-protector-flags-to-workaround-musl-bui.patch"
 
 PAM_PLUGINS = " \
     pam-plugin-unix \
-- 
2.7.4



  parent reply	other threads:[~2019-01-12  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12  9:22 [PATCH 0/4] ppc/musl: Improve support Serhey Popovych
2019-01-12  9:22 ` [PATCH 1/4] systemd: Correctly check ENABLE_GSHADOW with if/endif Serhey Popovych
2019-01-12  9:22 ` Serhey Popovych [this message]
2019-01-12 15:35   ` [PATCH 2/4] systemd: Use arch overrides instead of machine Khem Raj
2019-01-12  9:22 ` [PATCH 3/4] mpfr: Disable float128 when building with musl as libc Serhey Popovych
2019-01-12  9:22 ` [PATCH 4/4] valgrind: Mark powerpc64 with musl as incompatible Serhey Popovych
2019-01-12 15:29   ` Khem Raj
2019-01-12 16:53     ` Serhey Popovych
2019-01-12 18:30       ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1547284970-20783-3-git-send-email-serhe.popovych@gmail.com \
    --to=serhe.popovych@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox