From: Jan Viktorin <viktorin@rehivetech.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] Fw: dpdk-armv7 - Build # 342 - Failure!
Date: Fri, 11 Mar 2016 12:39:10 +0100 [thread overview]
Message-ID: <20160311123910.779f9c2e@jvn> (raw)
Hello Sergio,
I've detected a build regression for the ARMv7. It seems to me the
source of the problem is the following commit:
http://dpdk.org/browse/dpdk/commit/?id=d299106e8e31a622b3a1c1653f7795fa8a55860e
The ipsec-secgw should be compiled only when LPM is enabled. See, eg.
how the l3fwd-power example is done in examples/Makefile.
See the attached log file for details.
Regards
Jan Viktorin
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
next reply other threads:[~2016-03-11 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:39 Jan Viktorin [this message]
2016-03-11 11:47 ` Sergio Gonzalez Monroy
2016-03-11 13:33 ` Thomas Monjalon
2016-03-11 14:53 ` Sergio Gonzalez Monroy
2016-03-11 15:04 ` Thomas Monjalon
2016-03-11 15:11 ` Sergio Gonzalez Monroy
2016-03-11 15:18 ` 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=20160311123910.779f9c2e@jvn \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@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).