From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] build error on git checkout
Date: Mon, 20 Jun 2016 11:23:13 +0530 [thread overview]
Message-ID: <CAEXHiZHCSMNMbpxdfpvv7h0ZziBd4qo0D7wkXV6zNFjz+21peg@mail.gmail.com> (raw)
hi,
while building dpdk from a latest git checkout, i am seeing the following
build errors:
,----
| == Build lib/librte_eal/linuxapp/kni
| CC [M]
<...>/dpdk-sources/build/build/lib/librte_eal/linuxapp/kni/ixgbe_82599.o
| <...>/dpdk-sources/build/build/lib/librte_eal/linuxapp/kni/ixgbe_82599.c:
In function 'ixgbe_setup_mac_link_82599':
|
<...>/dpdk-sources/build/build/lib/librte_eal/linuxapp/kni/ixgbe_82599.c:870:3:
error: this 'if' clause does not guard... [-Werror=misleading-indentation]
| if (speed & IXGBE_LINK_SPEED_10GB_FULL)
| ^~
|
<...>/dpdk-sources/build/build/lib/librte_eal/linuxapp/kni/ixgbe_82599.c:873:4:
note: ...this statement, but the latter is misleadingly indented as if it
is guarded by the 'if'
| if ((orig_autoc & IXGBE_AUTOC_KR_SUPP) &&
| ^~
| cc1: all warnings being treated as errors
`----
similar error is also seen for
<...>/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_phy.c in
e1000_read_phy_reg_mphy(...) and e1000_write_phy_reg_mphy(...) as well.
build environment details:
dpdk-devel% uname -a
Linux dpdk-devel 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016
x86_64 GNU/Linux
dpdk-devel%
dpdk-devel% gcc --version
gcc (GCC) 6.1.1 20160602
Copyright (C) 2016 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.
--
thanks
anupam
next reply other threads:[~2016-06-20 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 5:53 Anupam Kapoor [this message]
2016-06-20 11:11 ` Ferruh Yigit
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=CAEXHiZHCSMNMbpxdfpvv7h0ZziBd4qo0D7wkXV6zNFjz+21peg@mail.gmail.com \
--to=anupam.kapoor@gmail.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).