DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vasiliy Tolstov <v.tolstov@selfip.ru>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] unable to compile 1.6.0
Date: Mon, 28 Apr 2014 08:28:46 +0400	[thread overview]
Message-ID: <CACaajQvUPUjYy9La4vtOBREHnU-YZWmSZaxRZBfWPyZCATRWyw@mail.gmail.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772580EFA0F07@IRSMSX105.ger.corp.intel.com>

2014-04-25 17:03 GMT+04:00 Ananyev, Konstantin <konstantin.ananyev@intel.com>:
> Then I suppose you need to set
> CONFIG_RTE_MACHINE="default"
> in your config file.


Thanks, this is works fine..., but:
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/internal/rte.compile-pre.mk:126:
recipe for target 'eal_common_cpuflags.o' failed
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/lib/librte_eal/common/eal_common_cpuflags.c:
In function 'rte_cpu_check_supported':
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/lib/librte_eal/common/eal_common_cpuflags.c:253:4:
error: 'RTE_COMPILE_TIME_CPUFLAGS' undeclared (first use in this
function)
    RTE_COMPILE_TIME_CPUFLAGS

Why this happening?

-- 
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru

  reply	other threads:[~2014-04-28  4:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  6:00 Vasiliy Tolstov
2014-04-25 11:20 ` Neil Horman
2014-04-25 11:36   ` Vasiliy Tolstov
2014-04-25 12:22     ` Ananyev, Konstantin
2014-04-25 12:36       ` Vasiliy Tolstov
2014-04-25 13:03         ` Ananyev, Konstantin
2014-04-28  4:28           ` Vasiliy Tolstov [this message]
2014-04-25 14:02         ` Paul Barrette
2014-04-28  3:28           ` Vasiliy Tolstov
2014-04-25 11:26 ` 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=CACaajQvUPUjYy9La4vtOBREHnU-YZWmSZaxRZBfWPyZCATRWyw@mail.gmail.com \
    --to=v.tolstov@selfip.ru \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).