All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 576] "‘str2flowtype’ defined but not used" when building with net/i40e disabled
Date: Thu, 12 Nov 2020 07:53:53 +0000	[thread overview]
Message-ID: <bug-576-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 576
           Summary: "‘str2flowtype’ defined but not used" when building
                    with net/i40e disabled
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: karol.latecki@intel.com
  Target Milestone: ---

When building with -Ddisable_drivers=net/i40e option, testpmd will give
warning:


../app/test-pmd/cmdline.c:10098:1: error: ‘str2flowtype’ defined but not used
[-Werror=unused-function]
10098 | str2flowtype(char *string)
      | ^~~~~~~~~~~~
cc1: all warnings being treated as errors


Also results in an error with -Werror.


Repruduction:

1. Using DPDK main branch with commit a8adac0bc098dad9ca7f7977b6204b29669244e8
2. meson build-tmp --libdir lib -Denable_docs=false -Denable_kmods=false
-Dtests=false -Dc_link_args= '-Dc_args=-fPIC -g -Werror -fcommon
-Wno-stringop-overflow' -Dmachine=native -Ddisable_drivers=net/i40e
3. ninja -C ./build-tmp install

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

             reply	other threads:[~2020-11-12  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  7:53 bugzilla [this message]
2021-01-29  8:23 ` [dpdk-dev] [Bug 576] "‘str2flowtype’ defined but not used" when building with net/i40e disabled 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-576-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.