Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joe Slater <jslater@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 1/1] allarch: do not set baselib
Date: Tue, 2 Jan 2018 12:00:49 -0800	[thread overview]
Message-ID: <20180102200049.44793-1-jslater@windriver.com> (raw)

postinstall scripts may run target binaries and need to know
where shared libraries are.

Signed-off-by: Joe Slater <jslater@windriver.com>
---
 meta/classes/allarch.bbclass | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta/classes/allarch.bbclass b/meta/classes/allarch.bbclass
index 51ba509..3749328 100644
--- a/meta/classes/allarch.bbclass
+++ b/meta/classes/allarch.bbclass
@@ -11,9 +11,8 @@ python () {
         # No need for virtual/libc or a cross compiler
         d.setVar("INHIBIT_DEFAULT_DEPS","1")
 
-        # Set these to a common set of values, we shouldn't be using them other that for WORKDIR directory
-        # naming anyway
-        d.setVar("baselib", "lib")
+        # Set these to a common set of values, we shouldn't be using them other than for WORKDIR directory
+        # naming anyway.  Do not set baselib because postinstall may need to know where shared libraries are.
         d.setVar("TARGET_ARCH", "allarch")
         d.setVar("TARGET_OS", "linux")
         d.setVar("TARGET_CC_ARCH", "none")
-- 
2.7.4



             reply	other threads:[~2018-01-02 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 20:00 Joe Slater [this message]
2018-01-02 22:45 ` [PATCH 1/1] allarch: do not set baselib Richard Purdie
2018-01-03  8:43   ` Alexander Kanavin
2018-01-03 21:46     ` Slater, Joseph
2018-01-03 21:58       ` Richard Purdie
2018-01-04 17:24         ` Slater, Joseph
2018-01-03 21:56     ` Richard Purdie

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=20180102200049.44793-1-jslater@windriver.com \
    --to=jslater@windriver.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