From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Jan Viktorin <viktorin@rehivetech.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
nd <nd@arm.com>, "J.Grant@qub.ac.uk" <J.Grant@qub.ac.uk>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] eal/arm: enable FreeBSD build
Date: Fri, 11 Jun 2021 10:49:41 +0000 [thread overview]
Message-ID: <AM5PR0802MB2465BCC2AA76358C22EEDC4C9E349@AM5PR0802MB2465.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8ywF_HO7n7YonpKzaPvgByEKXntzS3Wg2upMEi_rSnxGQ@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, June 11, 2021 4:59 PM
> To: Ruifeng Wang <Ruifeng.Wang@arm.com>
> Cc: Jan Viktorin <viktorin@rehivetech.com>; jerinj@marvell.com; Bruce
> Richardson <bruce.richardson@intel.com>; dev <dev@dpdk.org>; nd
> <nd@arm.com>; J.Grant@qub.ac.uk; thomas@monjalon.net; Honnappa
> Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Subject: Re: [PATCH] eal/arm: enable FreeBSD build
>
> On Fri, Jun 4, 2021 at 7:49 AM Ruifeng Wang <ruifeng.wang@arm.com>
> wrote:
> >
> > Build on FreeBSD on aarch64 failed with error:
> > lib/eal/arm/rte_cpuflags.c:86:9: error: unknown type name 'Elf64_auxv_t'
> >
> > The data type is used by OS Linux auxiliary vector read, and not used
> > by arch specific cpu flag API implementations. Hence remove it from Arm
> file.
> >
> > Reported-by: James Grant <j.grant@qub.ac.uk>
> > Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
>
> This never worked, so this patch counts as enabling a new supported OS/arch.
>
> If we want FreeBSD support on ARM, we will need non regression tests in
> some CI.
Currently no plan to claim FreeBSD support on Arm.
I'll update commit message to treat it as removal of useless code.
> A release notes update is also needed.
>
>
> --
> David Marchand
next prev parent reply other threads:[~2021-06-11 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 5:48 Ruifeng Wang
2021-06-04 9:32 ` James Grant
2021-06-11 8:58 ` David Marchand
2021-06-11 10:49 ` Ruifeng Wang [this message]
2021-06-11 14:42 ` [dpdk-dev] [PATCH v2] eal/arm: remove irrelevant code Ruifeng Wang
2021-07-05 7:54 ` David Marchand
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=AM5PR0802MB2465BCC2AA76358C22EEDC4C9E349@AM5PR0802MB2465.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=J.Grant@qub.ac.uk \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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;
as well as URLs for NNTP newsgroup(s).