From: Stefan Agner <stefan@agner.ch>
To: openembedded-core@lists.openembedded.org
Cc: Stefan Agner <stefan.agner@toradex.com>, otavio@ossystems.com.br
Subject: [PATCH] waf.bbclass: explicitly pass libdir
Date: Mon, 11 Dec 2017 14:57:20 +0100 [thread overview]
Message-ID: <20171211135720.38714-1-stefan@agner.ch> (raw)
From: Stefan Agner <stefan.agner@toradex.com>
On some build hosts distros (e.g. Fedora 26) waf tries to be
smart about libdir detection and defaults to [EXEC_PREFIX/lib64].
This obviously is not what we want for 32-bit targets and usually
fails in the do_package phase:
WARNING: gstreamer1.0-plugins-imx-0.13.0-r0 do_package: QA Issue: gstreamer1.0-plugins-imx: Files/directories were installed but not shipped in any package:
/usr/lib64/libgstimxcommon.so.0
Explicitly pass libdir to waf reliably resolves the issue.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
---
meta/classes/waf.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/waf.bbclass b/meta/classes/waf.bbclass
index c4698e910a..43b3f098ac 100644
--- a/meta/classes/waf.bbclass
+++ b/meta/classes/waf.bbclass
@@ -26,7 +26,7 @@ def get_waf_parallel_make(d):
return ""
waf_do_configure() {
- ${S}/waf configure --prefix=${prefix} ${EXTRA_OECONF}
+ ${S}/waf configure --prefix=${prefix} --libdir=${libdir} ${EXTRA_OECONF}
}
waf_do_compile() {
--
2.13.6
next reply other threads:[~2017-12-11 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 13:57 Stefan Agner [this message]
2017-12-11 14:01 ` [PATCH] waf.bbclass: explicitly pass libdir Burton, Ross
2017-12-11 14:16 ` Stefan Agner
2017-12-11 14:58 ` Burton, Ross
2017-12-11 15:32 ` Joshua Watt
2017-12-11 15:37 ` Joshua Watt
2017-12-11 17:09 ` Burton, Ross
2017-12-11 17:15 ` Otavio Salvador
2017-12-12 7:48 ` Stefan Agner
2017-12-12 10:58 ` Burton, Ross
2017-12-12 11:07 ` Stefan Agner
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=20171211135720.38714-1-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=stefan.agner@toradex.com \
/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