From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-webserver][PATCH 1/2] apache2: Correct appending to SYSROOT_PREPROCESS_FUNCS
Date: Sat, 20 Apr 2019 01:56:01 +0200 [thread overview]
Message-ID: <20190419235602.3553-1-pkj@axis.com> (raw)
A missing space lead to problems if something else was already added to
SYSROOT_PREPROCESS_FUNCS.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
We have a bbappend which amongst others inherits useradd, which also
appends to SYSROOT_PREPROCESS_FUNCS. What really confuses me though,
is that there was no error due to not being able to find the non-
existent useradd_sysroot_sstateapache_sysroot_preprocess function...
Only reason I noticed that there was a problem was because other
packages failed to build because apxs had not been installed in the
sysroot as expected.
meta-webserver/recipes-httpd/apache2/apache2_2.4.39.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-webserver/recipes-httpd/apache2/apache2_2.4.39.bb b/meta-webserver/recipes-httpd/apache2/apache2_2.4.39.bb
index d58ccb8f2..c6961ef9b 100644
--- a/meta-webserver/recipes-httpd/apache2/apache2_2.4.39.bb
+++ b/meta-webserver/recipes-httpd/apache2/apache2_2.4.39.bb
@@ -147,7 +147,7 @@ do_install_append_class-native() {
install -m 755 server/gen_test_char ${D}${bindir}
}
-SYSROOT_PREPROCESS_FUNCS_append_class-target = "apache_sysroot_preprocess"
+SYSROOT_PREPROCESS_FUNCS_append_class-target = " apache_sysroot_preprocess"
apache_sysroot_preprocess() {
install -d ${SYSROOT_DESTDIR}${bindir_crossscripts}
--
2.12.0
next reply other threads:[~2019-04-19 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 23:56 Peter Kjellerstedt [this message]
2019-04-19 23:56 ` [meta-webserver][PATCH 2/2] apache2: Correct packaging of build and doc related files Peter Kjellerstedt
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=20190419235602.3553-1-pkj@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-devel@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