DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Prashant Upadhyaya <praupadhyaya@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] compilation error with 1.6.0r2
Date: Thu, 22 May 2014 16:31:35 +0200	[thread overview]
Message-ID: <1603617.4BLVj11sf6@xps13> (raw)
In-Reply-To: <CAPBAu3U4HrFUT6FaK+A+DWi6x+qDiSuGBhdZz2iQccnsQqgLSQ@mail.gmail.com>

Hi Prashant,

2014-05-15 20:14, Prashant Upadhyaya:
> Hi,
> 
> I recently picked the 1.6.0r2 from dpdk.org and tried to compile it the
> usual way and ran into the following compilation error.
> 
> I am aware I can sidestep these by getting the compiler to treat them as
> warnings, but these did not use to come with 1.6.0r1 so wanted to report it
> here.
> 
> I am using Fedora 18 to compile this version of DPDK.
[...]
> /root/dpdk-1.6.0r2/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp
> /kni/igb_ethtool.c: In function 'igb_get_eee':
> 
> */root/dpdk-1.6.0r2/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxap
> p/kni/igb_ethtool.c:2441:4: error: implicit declaration of function
> 'mmd_eee_adv_to_ethtool_adv_t' [-Werror=implicit-function-declaration]*
> 
> /root/dpdk-1.6.0r2/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp
> /kni/igb_ethtool.c: In function 'igb_set_eee':
> 
> */root/dpdk-1.6.0r2/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxap
> p/kni/igb_ethtool.c:2551:2: error: implicit declaration of function
> 'ethtool_adv_to_mmd_eee_adv_t' [-Werror=implicit-function-declaration]*

It should be fixed in 1.7.0 in this commit:
	http://dpdk.org/browse/dpdk/commit/?id=d719bc02aa4acdc

Thanks for reporting
-- 
Thomas

  reply	other threads:[~2014-05-22 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 14:44 Prashant Upadhyaya
2014-05-22 14:31 ` Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-12  8:45 Prashant Upadhyaya
2014-05-12  9:11 ` Thomas Monjalon
2014-05-12 11:33   ` Neil Horman

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=1603617.4BLVj11sf6@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=praupadhyaya@gmail.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).