From: Denys Dmytriyenko <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] nativesdk-libtool: sanitize the script, remove buildpaths
Date: Wed, 17 Jul 2024 13:16:47 -0400 [thread overview]
Message-ID: <20240717171647.GF17572@denix.org> (raw)
In-Reply-To: <7f395fd1db119b4d0b6777bdb17aa4572b45bb97.camel@linuxfoundation.org>
On Wed, Jul 17, 2024 at 07:29:45AM +0100, Richard Purdie wrote:
> On Tue, 2024-07-16 at 18:09 -0400, Denys Dmytriyenko via lists.openembedded.org wrote:
> > From: Denys Dmytriyenko <denys@konsulko.com>
> >
> > Copy the same sed command to sanitize libtool script from target recipe
> > to nativesdk one. Otherwise fails with buildpaths QA error:
> >
> > ERROR: nativesdk-libtool-2.5.0-r0 do_package_qa: QA Issue: File /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/usr/bin/libtool in package nativesdk-libtool contains reference to TMPDIR [buildpaths]
> >
> > Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> > ---
> > .../libtool/nativesdk-libtool_2.5.0.bb | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/meta/recipes-devtools/libtool/nativesdk-libtool_2.5.0.bb b/meta/recipes-devtools/libtool/nativesdk-libtool_2.5.0.bb
> > index ddb60e717c..69de7a8e40 100644
> > --- a/meta/recipes-devtools/libtool/nativesdk-libtool_2.5.0.bb
> > +++ b/meta/recipes-devtools/libtool/nativesdk-libtool_2.5.0.bb
> > @@ -13,6 +13,18 @@ do_install () {
> > autotools_do_install
> > install -d ${D}${bindir}/
> > install -m 0755 libtool ${D}${bindir}/
> > +
> > + sed -e 's@--sysroot=${STAGING_DIR_HOST}@@g' \
> > + -e "s@${DEBUG_PREFIX_MAP}@@g" \
> > + -e 's@${STAGING_DIR_HOST}@@g' \
> > + -e 's@${STAGING_DIR_NATIVE}@@g' \
> > + -e 's@^\(sys_lib_search_path_spec="\).*@\1${libdir} ${base_libdir}"@' \
> > + -e 's@^\(compiler_lib_search_dirs="\).*@\1${libdir} ${base_libdir}"@' \
> > + -e 's@^\(compiler_lib_search_path="\).*@\1${libdir} ${base_libdir}"@' \
> > + -e 's@^\(predep_objects="\).*@\1"@' \
> > + -e 's@^\(postdep_objects="\).*@\1"@' \
> > + -e "s@${HOSTTOOLS_DIR}/@@g" \
> > + -i ${D}${bindir}/libtool
> > }
> >
> > SYSROOT_PREPROCESS_FUNCS += "libtoolnativesdk_sysroot_preprocess"
> >
>
> Rather than duplicate code, particularly long commands like this, it
> should be moved to a function and called from both locations.
v2 submitted.
--
Denys
prev parent reply other threads:[~2024-07-17 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 22:09 [PATCH] nativesdk-libtool: sanitize the script, remove buildpaths Denys Dmytriyenko
2024-07-17 6:29 ` [OE-core] " Richard Purdie
2024-07-17 17:16 ` Denys Dmytriyenko [this message]
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=20240717171647.GF17572@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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