Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix
Date: Tue, 28 Jan 2020 15:16:41 +0000	[thread overview]
Message-ID: <20200128151643.9711-3-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20200128151643.9711-1-richard.purdie@linuxfoundation.org>

Now we have recipe specific sysroots we don't need this native path
prefix. It was breaking the crosssdk/cross-canadian cases and causing
bugs, removing it is the simplest solution.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 meta/classes/texinfo.bbclass                                  | 4 +---
 .../texinfo-dummy-native/texinfo-dummy-native.bb              | 2 --
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/meta/classes/texinfo.bbclass b/meta/classes/texinfo.bbclass
index 6b0def0eac4..72091c733e5 100644
--- a/meta/classes/texinfo.bbclass
+++ b/meta/classes/texinfo.bbclass
@@ -10,9 +10,7 @@ TEXDEP = "texinfo-native"
 TEXDEP_class-native = "texinfo-dummy-native"
 TEXDEP_class-cross = "texinfo-dummy-native"
 DEPENDS_append = " ${TEXDEP}"
-PATH_prepend_class-native = "${STAGING_BINDIR_NATIVE}/texinfo-dummy-native:"
-PATH_prepend_class-cross = "${STAGING_BINDIR_NATIVE}/texinfo-dummy-native:"
 
 # libtool-cross doesn't inherit cross
 TEXDEP_pn-libtool-cross = "texinfo-dummy-native"
-PATH_prepend_pn-libtool-cross = "${STAGING_BINDIR_NATIVE}/texinfo-dummy-native:"
+
diff --git a/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb b/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb
index 1254bc89b48..3e6dfb0f1b9 100644
--- a/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb
+++ b/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb
@@ -9,8 +9,6 @@ SRC_URI = "file://template.py file://COPYING"
 
 S = "${WORKDIR}"
 
-NATIVE_PACKAGE_PATH_SUFFIX = "/${PN}"
-
 inherit native
 
 do_install_name() {
-- 
2.20.1



  parent reply	other threads:[~2020-01-28 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 15:16 [PATCH 1/5] bc: Use texinfo class Richard Purdie
2020-01-28 15:16 ` [PATCH 2/5] glibc-package.inc: Remove warnings about unpacked directories Richard Purdie
2020-01-28 15:16 ` Richard Purdie [this message]
2020-01-29  2:00   ` [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix Khem Raj
2020-01-29 11:59     ` Richard Purdie
2020-01-29 16:02       ` Khem Raj
2020-01-28 15:16 ` [PATCH 4/5] texinfo: Only build texinfo when api-docs enabled Richard Purdie
2020-01-28 15:16 ` [PATCH 5/5] bitbake.conf/sanity: Drop makeinfo as being required on buildhost Richard Purdie
2020-01-28 15:58 ` [PATCH 1/5] bc: Use texinfo class Jacob Kroon
2020-01-28 16:18   ` 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=20200128151643.9711-3-richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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