From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix build
Date: Thu, 30 Jul 2015 02:10:20 +0200 [thread overview]
Message-ID: <2524437.tIIWBSmXf7@xps13> (raw)
In-Reply-To: <4566288.d5QVtI4JvI@xps13>
2015-07-29 17:08, Thomas Monjalon:
> 2015-07-29 15:00, Zhang, Helin:
> > /home/hzhan75/r22/isg_cid-dpdk_org/lib/librte_eal/common/eal_common_pci.c: In function �rte_eal_pci_probe_one_driver’:
> > /home/hzhan75/r22/isg_cid-dpdk_org/lib/librte_eal/common/eal_common_pci.c:188:4: error: implicit declaration of function �pci_config_space_set’ [-Werror=implicit-function-declaration]
> > pci_config_space_set(dev);
> > ^
> > /home/hzhan75/r22/isg_cid-dpdk_org/lib/librte_eal/common/eal_common_pci.c:188:4: error: nested extern declaration of �pci_config_space_set’ [-Werror=nested-externs]
> > cc1: all warnings being treated as errors
> > /home/hzhan75/r22/isg_cid-dpdk_org/lib/librte_eal/linuxapp/eal/eal_pci.c:561:1: error: �pci_config_space_set’ defined but not used [-Werror=unused-function]
> > pci_config_space_set(struct rte_pci_device *dev)
> > ^
> > cc1: all warnings being treated as errors
>
> So I will change the title to:
> eal: fix build with pci config enabled
>
> and add this into the message:
> Build log:
> lib/librte_eal/common/eal_common_pci.c:188:4: error:
> implicit declaration of function pci_config_space_set
>
>
> > > 2015-07-29 06:48, Helin Zhang:
> > > > It fixes the build error of implicit declaration of function.
Applied, thanks
prev parent reply other threads:[~2015-07-30 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 22:48 Helin Zhang
2015-07-29 8:19 ` Thomas Monjalon
2015-07-29 15:00 ` Zhang, Helin
2015-07-29 15:05 ` Gonzalez Monroy, Sergio
2015-07-29 15:09 ` Zhang, Helin
2015-07-29 16:05 ` Thomas Monjalon
2015-07-29 16:10 ` Zhang, Helin
2015-07-29 15:08 ` Thomas Monjalon
2015-07-29 15:18 ` Zhang, Helin
2015-07-30 0:10 ` Thomas Monjalon [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=2524437.tIIWBSmXf7@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.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).