From: Panu Matilainen <pmatilai@redhat.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>,
dev@dpdk.org, Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH] config: add default linux configuration
Date: Fri, 12 Feb 2016 14:31:45 +0200 [thread overview]
Message-ID: <56BDD0B1.9040502@redhat.com> (raw)
In-Reply-To: <1453991505-15205-1-git-send-email-bernard.iremonger@intel.com>
On 01/28/2016 04:31 PM, Bernard Iremonger wrote:
> add config/defconfig_x86_64-default-linuxapp-gcc file.
>
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> ---
> config/defconfig_x86_64-default-linuxapp-gcc | 42 ++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
> create mode 100644 config/defconfig_x86_64-default-linuxapp-gcc
>
There was a related discussion back in March, see
http://dpdk.org/ml/archives/dev/2015-March/014626.html
I intended to go with that and submit patch(es) but the amount of
duplication and new files gets mind-numbing when you make them for all
existing targets. In other words, this approach doesn't scale.
Thomas, I remember seeing a plan to include a configure script in DPDK
many times in past months. Do you have something specific in mind, ie
actually use autoconf or just a custom hand-written script named
"configure" that roughly resembles autoconf configure or...?
- Panu -
next prev parent reply other threads:[~2016-02-12 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 14:31 [PATCH] config: add default linux configuration Bernard Iremonger
2016-02-12 12:31 ` Panu Matilainen [this message]
2016-02-12 15:04 ` Thomas Monjalon
2016-02-12 16:59 ` Ferruh Yigit
2016-02-12 17:13 ` Thomas Monjalon
2016-02-12 17:23 ` Ferruh Yigit
2016-02-16 11:16 ` Ferruh Yigit
2016-02-16 11:23 ` Thomas Monjalon
2016-02-16 12:08 ` Ferruh Yigit
2016-02-17 10:42 ` Iremonger, Bernard
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=56BDD0B1.9040502@redhat.com \
--to=pmatilai@redhat.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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.