From: Romulo Rosa <romuloros@gmail.com>
To: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problem with QEMU
Date: Sat, 7 Dec 2013 13:02:30 -0200 [thread overview]
Message-ID: <CALdSg2g6oDY==W4PUC=cpgWGck1LJrELTc=XMNk+ts=PugpMrg@mail.gmail.com> (raw)
In-Reply-To: <CAJn5u1=dKj3b1W8ien8qrhDD-eV3tKG_NLZn6zOPrdcBnK_Uzw@mail.gmail.com>
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?
2013/12/7 Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
> You need to compile DPDK with -fPIC option..
>
> -Jyoti
>
>
> On Sat, Dec 7, 2013 at 5:50 PM, Romulo Rosa <romuloros@gmail.com> wrote:
>
>> Hi,
>>
>> I'm trying to compile QEMU on Ubuntu 12:04 and'm having the following
>> problem:
>>
>> LINK x86_64-softmmu/qemu-system-x86_64
>> /usr/bin/ld:
>>
>> /home/xerifao/ovs_dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/lib/librte_eal.a(eal.o):
>> relocation R_X86_64_32 against `.rodata.str1.8' can not be used when
>> making
>> a shared object; recompile with -fPIC
>>
>> /home/xerifao/ovs_dpdk/dpdk-1.5.1r1/x86_64-default-linuxapp-gcc/lib/librte_eal.a:
>> could not read symbols: Bad value
>>
>> collect2: ld returned 1 exit status
>>
>>
>> The fPIC flag is setted on my Makefile:
>>
>> pixman/Makefile: $(SRC_PATH)/pixman/configure
>> (cd pixman; CFLAGS="$(CFLAGS) -fPIC $(extra_cflags)
>> $(extra_ldflags)" $(SRC_PATH)/pixman/configure $(AUTOCONF_HOST)
>> --disable-gtk --disable-shared --enable-static)
>>
>>
>> Anyone know how to help me?
>>
>> Thanks!
>>
>> --
>> Rômulo Rosa Furtado
>>
>
>
--
Rômulo Rosa Furtado
next prev parent reply other threads:[~2013-12-07 15:01 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 [this message]
2013-12-09 9:09 ` Thomas Monjalon
2013-12-09 9:58 ` Romulo Rosa
2013-12-09 11:15 ` Romulo Rosa
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='CALdSg2g6oDY==W4PUC=cpgWGck1LJrELTc=XMNk+ts=PugpMrg@mail.gmail.com' \
--to=romuloros@gmail.com \
--cc=dev@dpdk.org \
--cc=jyotisr5@googlemail.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).