DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dan Gora <dg@adax.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Multiple compilation failures in recent commits on branch master.
Date: Wed, 17 Oct 2018 20:44:30 -0300	[thread overview]
Message-ID: <CAGyogRb_ad3U9GeAcJycdptz80WLaP09R2QUMXOqqn4_fxiHVA@mail.gmail.com> (raw)

Hi All,

I sent a patch yesterday to fix a compilation failure in the
test_external_mem test and I pulled origin yesterday and now there is
another compilation failure which was introduced in commit
c3e0a706fd7595733cf51 (net/dpaa2: read hardware provided MAC for DPNI
devices):

/home/dg/Network_Fastpaths/dpdk/latest/drivers/net/dpaa2/dpaa2_ethdev.c:1849:9:
error: missing initializer for field ‘addr_bytes’ of ‘struct
ether_addr’ [-Werror=missing-
field-initializers]
 struct ether_addr phy_mac = {}, prime_mac = {};
        ^
In file included from
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ethdev.h:158:0,
                from
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ethdev_driver.h:18,
                from
/home/dg/Network_Fastpaths/dpdk/latest/drivers/net/dpaa2/dpaa2_ethdev.c:12:
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ether.h:58:10:
note: ‘addr_bytes’ declared here
 uint8_t addr_bytes[ETHER_ADDR_LEN]; /**< Addr bytes in tx order */
         ^
/home/dg/Network_Fastpaths/dpdk/latest/drivers/net/dpaa2/dpaa2_ethdev.c:1849:9:
error: missing initializer for field ‘addr_bytes’ of ‘struct
ether_addr’ [-Werror=missing-
field-initializers]
 struct ether_addr phy_mac = {}, prime_mac = {};
        ^
In file included from
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ethdev.h:158:0,
                from
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ethdev_driver.h:18,
                from
/home/dg/Network_Fastpaths/dpdk/latest/drivers/net/dpaa2/dpaa2_ethdev.c:12:
/home/dg/Network_Fastpaths/dpdk/latest/x86_64-native-linuxapp-gcc/include/rte_ether.h:58:10:
note: ‘addr_bytes’ declared here
 uint8_t addr_bytes[ETHER_ADDR_LEN]; /**< Addr bytes in tx order */
         ^
cc1: all warnings being treated as errors

Is something up where the automated compilation tests are not working?
 Is gcc 4.8.5 not supported any more?

I'm using stock OpenSuse 42.3 with gcc 4.8.5:

=> gcc --version
gcc (SUSE Linux) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

             reply	other threads:[~2018-10-17 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 23:44 Dan Gora [this message]
2018-10-17 23:51 ` Dan Gora

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=CAGyogRb_ad3U9GeAcJycdptz80WLaP09R2QUMXOqqn4_fxiHVA@mail.gmail.com \
    --to=dg@adax.com \
    --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).