From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>,
openembedded-core@lists.openembedded.org, ross.burton@intel.com
Subject: Re: [PATCH] libidn2: improve reproducibility
Date: Sat, 29 Sep 2018 13:30:12 +0100 [thread overview]
Message-ID: <f7670593f1d04dfe9e212a4b86d766fa3cdb60cb.camel@linuxfoundation.org> (raw)
In-Reply-To: <1538190383-31405-1-git-send-email-hongxu.jia@windriver.com>
On Sat, 2018-09-29 at 11:06 +0800, Hongxu Jia wrote:
> Remoe prefix ${RECIPE_SYSROOT} in libidn2.pc
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/recipes-extended/libidn/libidn2_2.0.5.bb | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> index 0daf7a6..7a06ed3 100644
> --- a/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> +++ b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
> @@ -27,3 +27,9 @@ LICENSE_${PN} = "(GPLv2+ | LGPLv3)"
> LICENSE_${PN}-bin = "GPLv3+"
>
> BBCLASSEXTEND = "native nativesdk"
> +
> +PACKAGE_PREPROCESS_FUNCS += "libidn2_package_preprocess"
> +libidn2_package_preprocess () {
> + sed -e 's@${RECIPE_SYSROOT}@@g' \
> + -i ${PKGD}${libdir}/pkgconfig/libidn2.pc
> +}
Why is RECIPE_SYSROOT in here in the first place? Can you include the
exact issue in the commit message?
I suspect there is probably a better fix than this.
On reason I hate sed expressions like this is that the sed expression
will sit there forever as its very hard to tell if it still applies
anymore. So more detail needed and it really probably should be a patch
of some sort.
Cheers,
Richard
next prev parent reply other threads:[~2018-09-29 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 3:06 [PATCH] libidn2: improve reproducibility Hongxu Jia
2018-09-29 12:30 ` Richard Purdie [this message]
2018-09-29 15:21 ` [PATCH V2] " Hongxu Jia
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=f7670593f1d04dfe9e212a4b86d766fa3cdb60cb.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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