From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] toolchain.eclass: Fix strip exclusion for prefixed cross-compilers
Date: Tue, 31 Dec 2024 10:04:06 +0000 [thread overview]
Message-ID: <5bc4fb16cbc45a7b7ab76e9778b8fba6bb46d4b3.camel@gentoo.org> (raw)
In-Reply-To: <Z3NXeSvqqAfNZb89@eversor>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
On Mon, 2024-12-30 at 21:31 -0500, Ionen Wolkens wrote:
> On Mon, Dec 30, 2024 at 11:35:25PM +0000, James Le Cuirot wrote:
> > dostrip limitations mean that we cannot strip the CTARGET binaries in a
> > cross-compiler. There is already a `dostrip -x` call to exclude such
> > binaries from stripping, but it expects the argument to be unprefixed,
> > and the argument given was prefixed.
> >
> > Signed-off-by: James Le Cuirot <chewi@gentoo.org>
> > ---
> > eclass/toolchain.eclass | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/eclass/toolchain.eclass b/eclass/toolchain.eclass
> > index 602f994371452..486b5877be66d 100644
> > --- a/eclass/toolchain.eclass
> > +++ b/eclass/toolchain.eclass
> > @@ -2641,7 +2641,7 @@ toolchain_src_install() {
> > # - "${D}${LIBPATH}"
> > # As dostrip does not specify host to override ${CHOST} tools just skip
> > # non-native binary stripping.
> > - is_crosscompile && dostrip -x "${LIBPATH}"
> > + is_crosscompile && dostrip -x "${LIBPATH#${EPREFIX}}"
>
> Missing quotes in case of unlikely globs in EPREFIX
>
> "${LIBPATH#"${EPREFIX}"}"
Ah yep, thanks. I always forget that weird rule.
> > cd "${S}" || die
> > if is_crosscompile; then
> > --
> > 2.47.1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
prev parent reply other threads:[~2024-12-31 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 23:35 [gentoo-dev] [PATCH] toolchain.eclass: Fix strip exclusion for prefixed cross-compilers James Le Cuirot
2024-12-31 2:31 ` Ionen Wolkens
2024-12-31 10:04 ` James Le Cuirot [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=5bc4fb16cbc45a7b7ab76e9778b8fba6bb46d4b3.camel@gentoo.org \
--to=chewi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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