DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 423] usertools/dpdk-setup.sh can not be used to run an application without compiling dpdk first
Date: Wed, 25 Mar 2020 09:04:56 +0000	[thread overview]
Message-ID: <bug-423-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 423
           Summary: usertools/dpdk-setup.sh can not be used to run an
                    application without compiling dpdk first
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: sarosh.arif@emumba.com
  Target Milestone: ---

When running an application using usertools/dpdk-setup.sh script, such as
testpmd, the following command is executed "sudo $RTE_TARGET/app/testpmd".
Where $RTE_TARGET is a variable, which is set when we compile dpdk using
dpdk-setup script, otherwise it is empty. So lets say a person has pre-compiled
dpdk and is just using the script to set hugepages and run testpmd, he would
have to recompile just to set the variable. 

This issue can be resolved by asking the user to enter the name of his build
directory if $RTE_TARGET is empty. The name entered by the user can then be
stored in $RTE_TARGET.  

I can submit a patch if this solution seems appropriate.

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

                 reply	other threads:[~2020-03-25  9:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-423-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).