From: Panu Matilainen <pmatilai@redhat.com>
To: Matthew Hall <mhall@mhcomputing.net>, "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vm_power_manager uses channel_commands.h which is not placed in installed copy of DPDK
Date: Mon, 15 Feb 2016 10:29:44 +0200 [thread overview]
Message-ID: <56C18C78.7080307@redhat.com> (raw)
In-Reply-To: <0863DE89-580E-4AA2-B949-25179510BD55@mhcomputing.net>
On 02/14/2016 01:38 AM, Matthew Hall wrote:
> Hello,
>
> I found a peculiarity in the vm_power_manager example on DPDK 2.2 if you use an installed copy of DPDK to compile the examples instead of the master copy (while trying to update some outdated stuff in my build system).
>
> mhall@mvs-01:~/dpdk/examples/vm_power_manager$ fgrep -ir channel_commands *.{c,h}
> channel_manager.c:#include "channel_commands.h"
> channel_monitor.c:#include "channel_commands.h"
> vm_power_cli.c:#include "channel_commands.h"
> channel_manager.h:#include "channel_commands.h"
>
> It appears a bunch of these files are trying to pull in this special header from here:
>
> /home/mhall/src/sdn_sensor/external/dpdk/lib/librte_power/channel_commands.h
>
> However this file is never copied into the include directions in the installed copy. So this example fails to build.
>
> Did anybody run into this before?
Yes, the problem exists at least since DPDK 2.1 but somehow never
remembered to report / do something about it.
Basically either vm_power_manager example is messing with things its not
supposed to, or librte_power library isn't exporting everything needed
to fully use the it. Unfortunately both the library and the example are
lacking a maintainer :-/
- Panu -
next prev parent reply other threads:[~2016-02-15 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 23:38 Matthew Hall
2016-02-15 8:29 ` Panu Matilainen [this message]
2016-02-15 10:15 ` Thomas Monjalon
2016-02-15 11:56 ` Panu Matilainen
2016-02-15 13:21 ` Thomas Monjalon
2016-02-15 18:03 ` Mcnamara, John
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=56C18C78.7080307@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).