From: Saint Michael <venefax@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] CONFIG_RTE_MACHINE
Date: Thu, 27 Aug 2020 07:28:18 -0400 [thread overview]
Message-ID: <CAC9cSOBzwB8Pj0NjH7mu19iCW5=zoQG66i-WVv4qSJ93EA=LdA@mail.gmail.com> (raw)
In-Reply-To: <CACtp79B-f1gGJj9mPZV0jhVJGrQ3JEayT_0nz62zSsgv_nq+ww@mail.gmail.com>
UNSUSCRIBE
On Thu, Aug 27, 2020 at 6:28 AM Jesse Grodman <jgrodman@gmail.com> wrote:
> Hello,
>
> I would like to use the config file in mk/machine/default/rte.vars.mk
> Per the docs, I have set CONFIG_RTE_MACHINE="default" in config/common_base
> However, CONFIG_RTE_MACHINE is still getting set to "native" in
> config/defconfig_x86_64-native-linux-gcc. I know this because when I
> commend out the line CONFIG_RTE_MACHINE="native" in
> config/defconfig_x86_64-native-linux-gcc, it is not overwritten, and my
> build uses mk/machine/default/rte.vars.mk
>
> What is the correct way to configure this?
>
> Thank you for your help,
> Jesse
>
prev parent reply other threads:[~2020-08-27 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 10:28 Jesse Grodman
2020-08-27 11:28 ` Saint Michael [this message]
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='CAC9cSOBzwB8Pj0NjH7mu19iCW5=zoQG66i-WVv4qSJ93EA=LdA@mail.gmail.com' \
--to=venefax@gmail.com \
--cc=users@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).