From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Building with 'make install T=' and 'make config T='
Date: Wed, 09 Dec 2015 18:52:50 +0100 [thread overview]
Message-ID: <4975020.B35JWah5pV@xps13> (raw)
In-Reply-To: <AB63BB58-F8DE-4444-AC32-13B973848DA5@intel.com>
2015-12-09 17:44, Wiles, Keith:
> On 12/9/15, 11:31 AM, "dev on behalf of Wiles, Keith" <dev-bounces@dpdk.org on behalf of keith.wiles@intel.com> wrote:
>
> >On 12/9/15, 10:19 AM, "Thomas Monjalon" <thomas.monjalon@6wind.com> wrote:
>
> BTW, I am not overly concerned about the build system per say I just wish I had put my $0.02 worth in before the change. We can leave as it is now.
>
> The test-build.sh script build does appear to be a real problem. I would like to understand why it does not work.
No your compilation error is a real problem.
The script enables some options which probably trigger the problem.
It is a script to test some compilation options.
Please check before doing some wrong assumptions. You are burning my time.
> Adding a better help message should be an easy fix for someone that wrote the script or I can make the changes, just let me know.
I will improve the help message.
next prev parent reply other threads:[~2015-12-09 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 14:39 Wiles, Keith
2015-12-09 14:59 ` Thomas Monjalon
2015-12-09 15:32 ` Wiles, Keith
2015-12-09 16:19 ` Thomas Monjalon
2015-12-09 17:31 ` Wiles, Keith
2015-12-09 17:44 ` Wiles, Keith
2015-12-09 17:52 ` Thomas Monjalon [this message]
2015-12-13 2:03 ` [dpdk-dev] [PATCH] scripts: add help for build testing Thomas Monjalon
2015-12-14 22:04 ` Thomas Monjalon
2015-12-09 17:56 ` [dpdk-dev] Building with 'make install T=' and 'make config T=' Thomas Monjalon
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=4975020.B35JWah5pV@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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 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).