From: Stephen Hemminger <stephen@networkplumber.org>
To: aisha <atammy.dpdk@bsd.ac>
Cc: dev@dpdk.org
Subject: Re: [patch] allow using standard ar from the build ini files instead of 'ar' string
Date: Mon, 28 Feb 2022 09:06:15 -0800 [thread overview]
Message-ID: <20220228090615.1ed89c35@hermes.local> (raw)
In-Reply-To: <bd9dd451-0af2-25af-ade6-bdf687d2de23@bsd.ac>
On Mon, 28 Feb 2022 10:54:28 -0500
aisha <atammy.dpdk@bsd.ac> wrote:
> Hi,
>
> I've attached a patch, from Gentoo, which uses the *ar* binary passed to
> meson when available, instead of 'ar', which may not be available, for
> instance when cross compiling, or having multiple gcc versions present,
> like in Gentoo.
>
> This should not have any regressions, as when the binary is not
> available it uses the same logic as the original.
>
> Aisha
>
Please resubmit this patch with proper Signed-off-by.
Without Developer's Certificate of Origin there can be license claims.
next prev parent reply other threads:[~2022-02-28 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 15:54 aisha
2022-02-28 17:06 ` Stephen Hemminger [this message]
2022-02-28 17:33 ` Bruce Richardson
2022-02-28 17:54 ` Bruce Richardson
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=20220228090615.1ed89c35@hermes.local \
--to=stephen@networkplumber.org \
--cc=atammy.dpdk@bsd.ac \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).