From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Jan Viktorin <viktorin@rehivetech.com>
Subject: Re: [dpdk-dev] Fw: dpdk-armv7 - Build # 342 - Failure!
Date: Fri, 11 Mar 2016 15:11:57 +0000 [thread overview]
Message-ID: <56E2E03D.2010901@intel.com> (raw)
In-Reply-To: <2101263.CINWvX51Cb@xps13>
On 11/03/2016 15:04, Thomas Monjalon wrote:
> 2016-03-11 14:53, Sergio Gonzalez Monroy:
>> On 11/03/2016 13:33, Thomas Monjalon wrote:
>>> 2016-03-11 11:47, Sergio Gonzalez Monroy:
>>>> On 11/03/2016 11:39, Jan Viktorin wrote:
>>>>> 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.
>>>> Right!
>>>>
>>>> Actually the app has dependencies on a few libraries, so I'll fix that.
>>> Please take the opportunity to move the crypto examples in the
>>> alphabetical order in this Makefile. Thanks
>>>
>>>
>> So the fix is easy enough but I'm really not a fan of cluttering the
>> examples/Makefile ifeq checks
>> which would only avoid building ipsec-secgw if doing:
>> $ make examples
>>
>> but would still fail to build if doing something like:
>> $ make -C examples/ipsec-secgw
> If you explicitly want to build this example, it is normal to fail.
Fair enough.
>> examples/Makefile:
>> +ifeq ($(CONFIG_RTE_LIBRTE_ACL),y)
>> +ifeq ($(CONFIG_RTE_LIBRTE_HASH),y)
>> +ifeq ($(CONFIG_RTE_LIBRTE_LPM),y)
>> DIRS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += ipsec-secgw
>> +endif
>> +endif
>> +endif
> You can do it in one line:
> ifeq ($(CONFIG_RTE_LIBRTE_ACL)$(CONFIG_RTE_LIBRTE_HASH)$(CONFIG_RTE_LIBRTE_LPM),yyy)
The line above goes to 85 chars, are you ok with that? or do I split it
in two lines?
Sergio
next prev parent reply other threads:[~2016-03-11 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:39 Jan Viktorin
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 [this message]
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=56E2E03D.2010901@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.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).