From: "Choi, Sy Jong" <sy.jong.choi@intel.com>
To: 'BYEONG-GI KIM' <kimbyeonggi@gmail.com>,
'Masaru Oki' <m-oki@stratosphere.co.jp>,
"'dev@dpdk.org'" <dev@dpdk.org>,
"'Dpdk-ovs@lists.01.org'" <Dpdk-ovs@lists.01.org>
Subject: Re: [dpdk-dev] Error while compiling DPDK
Date: Mon, 14 Jul 2014 02:40:32 +0000 [thread overview]
Message-ID: <697F8B1B48670548A5BAB03E8283550F2D300085@PGSMSX107.gar.corp.intel.com> (raw)
In-Reply-To: <CAEHt_JZY0YRJtouL-+jogCcyLazv1Rf41=0T_OOeKTP8imH2MQ@mail.gmail.com>
Hi Mr. Kim,
May confirm which environment are you using?
x86_64-default-linuxapp-gcc or
x86_64-native-linuxapp-gcc
Regards,
Choi, Sy Jong
-----Original Message-----
From: BYEONG-GI KIM [kimbyeonggi@gmail.com<mailto:kimbyeonggi@gmail.com>]
Sent: Monday, July 14, 2014 10:05 AM Malay Peninsula Standard Time
To: Masaru Oki; dev@dpdk.org; Dpdk-ovs@lists.01.org
Subject: Re: [dpdk-dev] Error while compiling DPDK
Here is the error message in English;
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
LD
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
CC [M]
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
Building modules, stage 2.
MODPOST 1 modules
CC
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
LD [M]
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
INSTALL-MODULE igb_uio.ko
== Build lib/librte_eal/linuxapp/eal
CC eal.o
gcc: error: –g: No such file or directory
make[7]: *** [eal.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
make: *** [install] Error 2
2014-07-14 11:02 GMT+09:00 Masaru Oki <m-oki@stratosphere.co.jp>:
> > I'm sorry for the Korean characteristics. It was shown because My Fedora
> OS
> > is set to use Korean as a default language.
>
> Try env LANG=C make install ...
>
>
> 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM <kimbyeonggi@gmail.com>:
>
>> Dear choi,
>>
>> Thank you for the reply.
>>
>> I've been trying to install DPDK while changing the command as you
>> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
>> shown;
>>
>>
>> [root@compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
>> ================== Installing x86_64-default-linuxapp-gcc
>> Configuration done
>> == Build scripts
>> == Build scripts/testhost
>> HOSTCC testhost.o
>> HOSTLD testhost
>> INSTALL-HOSTAPP testhost
>> == Build lib
>> == Build lib/librte_eal
>> == Build lib/librte_eal/common
>> SYMLINK-FILE include/rte_atomic.h
>> SYMLINK-FILE include/rte_branch_prediction.h
>> SYMLINK-FILE include/rte_byteorder.h
>> SYMLINK-FILE include/rte_common.h
>> SYMLINK-FILE include/rte_cycles.h
>> SYMLINK-FILE include/rte_debug.h
>> SYMLINK-FILE include/rte_eal.h
>> SYMLINK-FILE include/rte_errno.h
>> SYMLINK-FILE include/rte_launch.h
>> SYMLINK-FILE include/rte_lcore.h
>> SYMLINK-FILE include/rte_log.h
>> SYMLINK-FILE include/rte_memcpy.h
>> SYMLINK-FILE include/rte_memory.h
>> SYMLINK-FILE include/rte_memzone.h
>> SYMLINK-FILE include/rte_pci.h
>> SYMLINK-FILE include/rte_pci_dev_ids.h
>> SYMLINK-FILE include/rte_per_lcore.h
>> SYMLINK-FILE include/rte_prefetch.h
>> SYMLINK-FILE include/rte_random.h
>> SYMLINK-FILE include/rte_rwlock.h
>> SYMLINK-FILE include/rte_spinlock.h
>> SYMLINK-FILE include/rte_tailq.h
>> SYMLINK-FILE include/rte_interrupts.h
>> SYMLINK-FILE include/rte_alarm.h
>> SYMLINK-FILE include/rte_string_fns.h
>> SYMLINK-FILE include/rte_cpuflags.h
>> SYMLINK-FILE include/rte_version.h
>> SYMLINK-FILE include/rte_tailq_elem.h
>> SYMLINK-FILE include/rte_eal_memconfig.h
>> SYMLINK-FILE include/rte_malloc_heap.h
>> SYMLINK-FILE include/rte_hexdump.h
>> SYMLINK-FILE include/arch/rte_atomic.h
>> == Build lib/librte_eal/linuxapp
>> == Build lib/librte_eal/linuxapp/igb_uio
>> LD
>>
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>> CC [M]
>>
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>> Building modules, stage 2.
>> MODPOST 1 modules
>> CC
>>
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>> LD [M]
>>
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
>> INSTALL-MODULE igb_uio.ko
>> == Build lib/librte_eal/linuxapp/eal
>> CC eal.o
>> gcc: error: –g: 그런 파일이나 디렉터리가 없습니다
>> make[7]: *** [eal.o] 오류 1
>> make[6]: *** [eal] 오류 2
>> make[5]: *** [linuxapp] 오류 2
>> make[4]: *** [librte_eal] 오류 2
>> make[3]: *** [lib] 오류 2
>> make[2]: *** [all] 오류 2
>> make[1]: *** [x86_64-default-linuxapp-gcc_install] 오류 2
>> make: *** [install] 오류 2
>>
>> I'm sorry for the Korean characteristics. It was shown because My Fedora
>> OS
>> is set to use Korean as a default language.
>>
>> I set two environmental variables following the
>> intel-dpdk-programmers-guide.pdf as below:
>>
>> export RTE_SDK=/home/stack/dpdk/DPDK-1.6.0
>> export RTE_TARGET=x86_64-native-linuxapp-gcc
>>
>> What should I do in order to install DPDK successfully?...
>>
>> Thanks in advance.
>>
>> Best regards
>>
>> Byeong-Gi KIM
>>
>>
>>
>>
>> 2014-07-14 10:00 GMT+09:00 Choi, Sy Jong <sy.jong.choi@intel.com>:
>>
>> > Hi Mr. Kim,
>> >
>> > Please do not compile with "T=x86*gcc" because it will compile BSD app
>> > too, which cause the error.
>> >
>> > Please complile only the configuration you need. This should remove the
>> > error.
>> >
>> >
>> > Regards,
>> > Choi, Sy Jong
>> >
>> >
>> > -----Original Message-----
>> > *From: *BYEONG-GI KIM [kimbyeonggi@gmail.com]
>> > *Sent: *Monday, July 14, 2014 08:25 AM Malay Peninsula Standard Time
>> > *To: *Dpdk-ovs@lists.01.org; dev@dpdk.org
>> > *Subject: *[dpdk-dev] Error while compiling DPDK
>>
>> >
>> > Hello.
>> >
>> > An error occured while compiling DPDK 1.6.0r2 as below:
>> >
>> > [root@compute dpdk-1.6.0r2]# make install T=x86_64*gcc
>> > ...Installing...
>> > /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c: In function
>> > ‘rte_eal_init’:
>> > /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c:873:2: error:
>> > format ‘%p’ expects argument of type ‘void *’, but argument 5 has type
>> > ‘pthread_t’ [-Werror=format=]
>> > RTE_LOG(DEBUG, EAL, "Master core %u is ready (tid=%p)\n",
>> > ^
>> >
>> > The current OS is Fedora20. What should I do?...
>> >
>> > Best regards
>> >
>> > Byeong-Gi KIM
>> >
>>
>
>
next prev parent reply other threads:[~2014-07-14 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 0:24 BYEONG-GI KIM
2014-07-14 1:00 ` Choi, Sy Jong
2014-07-14 1:24 ` BYEONG-GI KIM
2014-07-14 2:02 ` Masaru Oki
2014-07-14 2:04 ` BYEONG-GI KIM
2014-07-14 2:40 ` Choi, Sy Jong [this message]
2014-07-14 3:28 ` BYEONG-GI KIM
2014-07-14 4:32 ` Choi, Sy Jong
2014-07-14 4:43 ` BYEONG-GI KIM
2014-07-14 8:27 ` De Lara Guarch, Pablo
2014-07-14 11:46 ` Neil Horman
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=697F8B1B48670548A5BAB03E8283550F2D300085@PGSMSX107.gar.corp.intel.com \
--to=sy.jong.choi@intel.com \
--cc=Dpdk-ovs@lists.01.org \
--cc=dev@dpdk.org \
--cc=kimbyeonggi@gmail.com \
--cc=m-oki@stratosphere.co.jp \
/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).