From: "Cao, Waterman" <waterman.cao@intel.com>
To: "Carew, Alan" <alan.carew@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] rte_tailq.h: Fix compilation under FreeBSD
Date: Tue, 10 Jun 2014 05:56:50 +0000 [thread overview]
Message-ID: <AA3F441F262C58498CD6D0C1801DE7EB0AA90685@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1401984728-21665-1-git-send-email-alan.carew@intel.com>
Tested-by: Waterman Cao <waterman.cao@intel.com>
This patch is to fix compilation error in the FreeBSD 10.0 like the followings:
.. /include/rte_tailq.h:177:21: error: unknown type name 'FILE' void rte_dump_tailq(FILE *f);
../include/rte_memory.h:146:30: error: unknown type name 'FILE' void rte_dump_physmem_layout(FILE *f);
After merged this patch with last dpdk.org, compilation can pass without error in FreeBSD 10.0
next prev parent reply other threads:[~2014-06-10 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 16:12 Alan Carew
2014-06-05 16:12 ` [dpdk-dev] [PATCH 2/2] eal_pci: " Alan Carew
2014-06-10 21:00 ` Bruce Richardson
2014-06-11 9:56 ` Thomas Monjalon
2014-06-10 5:56 ` Cao, Waterman [this message]
2014-06-10 20:58 ` [dpdk-dev] [PATCH 1/2] rte_tailq.h: " Bruce Richardson
2014-06-11 9:56 ` 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=AA3F441F262C58498CD6D0C1801DE7EB0AA90685@SHSMSX103.ccr.corp.intel.com \
--to=waterman.cao@intel.com \
--cc=alan.carew@intel.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).