From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>,
Neil Horman <nhorman@tuxdriver.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] unable to compile 1.6.0
Date: Fri, 25 Apr 2014 12:22:59 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580EFA0E86@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <CACaajQuBPFWjONEmJ91+Svngjbo2H6N1X9VnS-52mBf=cckiGQ@mail.gmail.com>
Hi Vasiliy,
Why just not use ' -cpu host' when starting your kvm?
Konstantin
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vasiliy Tolstov
Sent: Friday, April 25, 2014 12:37 PM
To: Neil Horman
Cc: dev
Subject: Re: [dpdk-dev] unable to compile 1.6.0
2014-04-25 15:20 GMT+04:00 Neil Horman <nhorman@tuxdriver.com>:
> Start by adding V=1 to your command line to start drilling down to where the
> problem is actually happening.
make -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/rte.sdkconfig.mk
config
if [ "/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc"
!= "" -a -f "/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc"
]; then \
cpp -undef -P -x assembler-with-cpp \
-fdirectives-only -ffreestanding \
-o /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/config/defconfig_x86_64-default-linuxapp-gcc
; \
if ! cmp -s
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config;
then \
cp
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config
; \
fi ; \
rm -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config_tmp
; \
else \
echo -n "No template specified. Use T=template " ; \
echo "among the following list:" ; \
for t in x86_64-ivshmem-linuxapp-icc
x86_64-ivshmem-linuxapp-gcc i686-default-linuxapp-icc
i686-default-linuxapp-gcc x86_64-default-linuxapp-icc
x86_64-default-bsdapp-gcc x86_64-default-linuxapp-gcc; do \
echo " $t" ; \
done ; \
fi
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/scripts/gen-build-mk.sh
../ build \
> /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/Makefile
rm -rf /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/include
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/app \
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/hostapp
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/lib \
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/hostlib
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/kmod
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/build
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/scripts/gen-config-h.sh
/var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/.config
\
> /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/build/include/rte_config.h
make depdirs
make -f /var/tmp/paludis/build/net-libs-dpdk-1.6.0/work/dpdk-1.6.0/mk/rte.sdkdepdirs.mk
depdirs
make -j3 -j3 V=1 config T=x86_64-default-linuxapp-gcc
As i see V=1 not passed down to other makefiles.
--
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru
next prev parent reply other threads:[~2014-04-25 12:23 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 [this message]
2014-04-25 12:36 ` Vasiliy Tolstov
2014-04-25 13:03 ` Ananyev, Konstantin
2014-04-28 4:28 ` Vasiliy Tolstov
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=2601191342CEEE43887BDE71AB9772580EFA0E86@IRSMSX105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=v.tolstov@selfip.ru \
/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).