From: Romulo Rosa <romuloros@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem with QEMU
Date: Mon, 9 Dec 2013 09:15:40 -0200 [thread overview]
Message-ID: <CALdSg2gh+KDKpeDXuTQzR3z-YaA_5Zzs+5REDMNfpFyfF8o43w@mail.gmail.com> (raw)
In-Reply-To: <CALdSg2gDTCH4-swtKaCaEFKL_zcKz0g=HheChLWVDtMzMpQK6w@mail.gmail.com>
Just to record how I solved the problem for those who might have the same
problem. Then run the command / configure - enable-kvm - dpdkdir = / path /
to / dpdk - target-list = x86_64-softmmu
--- a/dpdk-ovs/qemu/config-host.mak 2013-12-09 09:05:04.401122670 -0200
+++ b/dpdk-ovs/qemu/config-host.mak 2013-12-09 08:57:16.881103500 -0200
@@ -33,7 +33,10 @@
$(dpdk_lib_dir)/librte_mbuf.a \
$(dpdk_lib_dir)/librte_ring.a \
$(dpdk_lib_dir)/librte_mempool.a \
- $(dpdk_lib_dir)/librte_malloc.a
+ $(dpdk_lib_dir)/librte_malloc.a \
+ $(dpdk_lib_dir)/librte_pmd_ring.a \
+ $(dpdk_lib_dir)/libethdev.a
2013/12/9 Romulo Rosa <romuloros@gmail.com>
> Hello guys, thanks for the help. Yesterday I could compile with-fPIC
> however'm already trying to solve another problem in compiling QEMU. I had
> the same problem compiling ovs. Jyotiswarup Raiturkar helped me with OVS
> and I'm trying to adapt the solution to this case. If you already know how
> to appreciate the help again.
>
> /dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/lib/librte_eal.a(eal_common_nonpci_devs.o):(.data.rel+0x8):
> undefined reference to `rte_pmd_ring_init'
> collect2: ld returned 1 exit status
> make[1]: ** [qemu-system-x86_64] Erro 1
> make: ** [subdir-x86_64-softmmu] Erro 2
>
>
>
> 2013/12/9 Thomas Monjalon <thomas.monjalon@6wind.com>
>
>> 07/12/2013 16:02, Romulo Rosa :
>> > Thanks for the feedback. I compiled the DPDK with the -fPIC option. Is
>> > there any specific location in the Makefile DPDK where should I put the
>> > -fPIC option?
>>
>> You can use EXTRA_CFLAGS=-fPIC on the command line.
>>
>> --
>> Thomas
>>
>
>
>
> --
> Rômulo Rosa Furtado
>
--
Rômulo Rosa Furtado
next prev parent reply other threads:[~2013-12-09 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 12:20 Romulo Rosa
2013-12-07 14:02 ` Jyotiswarup Raiturkar
2013-12-07 15:02 ` Romulo Rosa
2013-12-09 9:09 ` Thomas Monjalon
2013-12-09 9:58 ` Romulo Rosa
2013-12-09 11:15 ` Romulo Rosa [this message]
2013-12-09 9:18 ` Jyotiswarup Raiturkar
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=CALdSg2gh+KDKpeDXuTQzR3z-YaA_5Zzs+5REDMNfpFyfF8o43w@mail.gmail.com \
--to=romuloros@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).