DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hamid Ramazani <mrramazani@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] g++: undefined reference to
Date: Fri, 3 Jan 2014 12:07:20 +0100	[thread overview]
Message-ID: <201401031207.20465.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CACu58pAnseukoEDJOkYOWX7=rGPhrHT2Jyn3bWND+hDjAwXdWg@mail.gmail.com>

Hello,

03/01/2014 11:48, Hamid Ramazani :
> eal_timer.c:(.text+0x42c): undefined reference to `clock_gettime'

From "man clock_gettime":
Link with -lrt (only for glibc versions before 2.17).

> 	g++ -m64 -pthread  -march=native -DRTE_MACHINE_CPUFLAG_SSE
> -DRTE_MACHINE_CPUFLAG_SSE2 -DRTE_MACHINE_CPUFLAG_SSSE3
> -DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2,RTE_CPUFLAG_SS
> SE3 -I/home/hamid/dpdk/dpdk-1.5.1r1/examples/sample/build/include
> -I/home/hamid/dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/include
> -include
> /home/hamid/dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/include/rte_conf
> ig.h -O3 -W -Wall -Werror -Wmissing-declarations -Wpointer-arith
> -Wcast-align -Wcast-qual -Wformat-nonliteral -Wformat-security -Wundef
> -Wwrite-strings -Wl,-melf_x86_64 -Wl,-export-dynamic sample.cpp -o
> sample -Wl,-L/home/hamid/dpdk/dpdk-1.5.1r1/examples/sample/build/lib
> -Wl,-L/home/hamid/dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/lib
> -Wl,-L/home/hamid/dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/lib
> -Wl,-lrte_kni -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ixgbe -Wl,-lrte_mbuf
> -Wl,-lrte_cmdline -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_lpm
> -Wl,--start-group -Wl,-lethdev -Wl,-lrte_malloc -Wl,-lrte_mempool
> -Wl,-lrte_ring -Wl,-lrte_eal -Wl,-ldl -Wl,--end-group

Try CONFIG_RTE_BUILD_COMBINE_LIBS=y and -lintel_dpdk instead of all these 
libraries. You can also remove the warning options if you want.

You can also try to build your Makefile by including files like 
mk/rte.extapp.mk and defining CC=g++.
I don't exactly know what is needed for C++. Please keep us informed.

-- 
Thomas

      reply	other threads:[~2014-01-03 11:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  9:35 Hamid Ramazani
2014-01-02 13:19 ` Stefan Baranoff
2014-01-02 16:40   ` Hamid Ramazani
     [not found]     ` <CAHzKxpZ0c8ryHxh3Nh-PEckKZD8a9XiYGy09ucgv4QjrFBPGbg@mail.gmail.com>
2014-01-03  0:46       ` Stefan Baranoff
2014-01-03 10:48         ` Hamid Ramazani
2014-01-03 11:07           ` Thomas Monjalon [this message]

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=201401031207.20465.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=mrramazani@gmail.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).