DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhan, Zhaochen" <zhaochen.zhan@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: fix build for bsd
Date: Wed, 2 Jul 2014 09:58:34 +0000	[thread overview]
Message-ID: <6D0EE020084B194084D70B0A8D2207B8E8EA6B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1404292944-5964-1-git-send-email-thomas.monjalon@6wind.com>

Hi 

I have tested the patch, it still has a build error although it is different from the previous one.

OS: FreeBSD10

== Build lib/librte_pmd_bond
  CC rte_eth_bond_api.o
/root/zzc/dpdk-1.7.0-rc3/lib/librte_pmd_bond/rte_eth_bond_api.c:35:27: fatal error: linux/binfmts.h: No such file or directory
 #include <linux/binfmts.h>
                           ^
compilation terminated.
gmake[5]: *** [rte_eth_bond_api.o] Error 1
gmake[4]: *** [librte_pmd_bond] Error 2
gmake[3]: *** [lib] Error 2
gmake[2]: *** [all] Error 2
gmake[1]: *** [x86_64-native-bsdapp-gcc_install] Error 2
gmake: *** [install] Error 2

Thanks,
Zhaochen

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, July 02, 2014 5:22 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] eal: fix build for bsd
> 
> When adding link bonding to EAL initialization (a155d430119),
> an include was missing for BSD.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
>  lib/librte_eal/bsdapp/eal/eal.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> 
> Please, a quick test and acknowledgement of this fix would be helpful.
> 
> 
> diff --git a/lib/librte_eal/bsdapp/eal/eal.c b/lib/librte_eal/bsdapp/eal/eal.c
> index ec57b26..69ead31 100644
> --- a/lib/librte_eal/bsdapp/eal/eal.c
> +++ b/lib/librte_eal/bsdapp/eal/eal.c
> @@ -66,6 +66,7 @@
>  #include <rte_cpuflags.h>
>  #include <rte_interrupts.h>
>  #include <rte_pci.h>
> +#include <rte_dev.h>
>  #include <rte_devargs.h>
>  #include <rte_common.h>
>  #include <rte_version.h>
> --
> 2.0.0

  reply	other threads:[~2014-07-02  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  2:38 [dpdk-dev] Compilation errors in FreeBSD and OR Linux (Kerne 2.6.39l Cao, Waterman
2014-07-02  9:22 ` [dpdk-dev] [PATCH] eal: fix build for bsd Thomas Monjalon
2014-07-02  9:58   ` Zhan, Zhaochen [this message]
2014-07-02 10:05     ` Thomas Monjalon

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=6D0EE020084B194084D70B0A8D2207B8E8EA6B@SHSMSX104.ccr.corp.intel.com \
    --to=zhaochen.zhan@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).