DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 237] Running test-build.sh Fails on ppc_64 fails due to hard-coded requirement for IXGBE_PMD in examples/vm_power_manager
Date: Tue, 02 Apr 2019 00:41:02 +0000	[thread overview]
Message-ID: <bug-237-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190402004102.QcdifGRhKFvE5pyLFw0plrsnkzhmw0bBelLuVR2epz4@z> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=237

            Bug ID: 237
           Summary: Running test-build.sh Fails on ppc_64 fails due to
                    hard-coded requirement for IXGBE_PMD in
                    examples/vm_power_manager
           Product: DPDK
           Version: 19.05
          Hardware: POWER
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: drc@linux.vnet.ibm.com
  Target Milestone: ---

The default configuration file config/defconfig_ppc_64-poweer8-linux-gcc
disables the IXGBE_PMD, indicating that it is not a tested adapter.  

The example application vm_power_manager has hard-coded dependencies on three
specific poll-mode drivers, including the IXGBE_PMD.

When running the devtools/test-build.sh script to verify a patch for IBM Power
systems, the script will fail because the include file rte_pmd_ixgbe.h, used by
 examples/vm_power_manager/main.c cannot be found. This results in the
test-build.sh script returning a failure even though any patch being tested
might be valid.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-04-02  0:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  0:41 bugzilla [this message]
2019-04-02  0:41 ` bugzilla
2020-04-26  0:46 ` bugzilla

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=bug-237-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).