DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] eal: fix build on armv7
Date: Fri, 24 Apr 2020 19:35:50 +0200	[thread overview]
Message-ID: <CAJFAV8zQRbTVgS3pMvwRR9cK+3qGfsj5sDU0YukB=HTx__H_0Q@mail.gmail.com> (raw)
In-Reply-To: <20200423142436.12810-1-david.marchand@redhat.com>

On Thu, Apr 23, 2020 at 4:25 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Caught by OBS on armv7:
>
> In file included from .../lib/librte_eal/include/rte_string_fns.h:21,
>                  from .../lib/librte_kvargs/rte_kvargs.c:9:
> .../lib/librte_eal/include/rte_common.h:67:37: error: expected '=', ',',
>  ';', 'asm' or '__attribute__' before '__rte_aligned'
>    67 | typedef uint64_t unaligned_uint64_t __rte_aligned(1);
>       |                                     ^~~~~~~~~~~~~
> .../lib/librte_eal/include/rte_common.h:68:37: error: expected '=', ',',
>  ';', 'asm' or '__attribute__' before '__rte_aligned'
>    68 | typedef uint32_t unaligned_uint32_t __rte_aligned(1);
>       |                                     ^~~~~~~~~~~~~
> .../lib/librte_eal/include/rte_common.h:69:37: error: expected '=', ',',
>  ';', 'asm' or '__attribute__' before '__rte_aligned'
>    69 | typedef uint16_t unaligned_uint16_t __rte_aligned(1);
>       |                                     ^~~~~~~~~~~~~
> make[3]: *** [.../mk/internal/rte.compile-pre.mk:116: rte_kvargs.o] Error 1
>
> Fixes: f35e5b3e07b2 ("replace alignment attributes")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>

Applied with mention of RTE_ARCH_STRICT_ALIGN in commitlog.


-- 
David Marchand


      parent reply	other threads:[~2020-04-24 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 14:24 David Marchand
2020-04-23 15:36 ` Thomas Monjalon
2020-04-24 17:35 ` David Marchand [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='CAJFAV8zQRbTVgS3pMvwRR9cK+3qGfsj5sDU0YukB=HTx__H_0Q@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).