From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v5 3/3] configure/Make: Build libfdt from submodule DTC
Date: Mon, 22 Apr 2013 10:58:43 +0200 [thread overview]
Message-ID: <5174FBC3.30707@redhat.com> (raw)
In-Reply-To: <CAEgOgz7_pWoJ2q=xUvVNkQyKjG0_jc-wCEtS_hPRUTQgBZDF1Q@mail.gmail.com>
Il 22/04/2013 06:45, Peter Crosthwaite ha scritto:
> Hi Paolo, Blue,
>
> On Sun, Apr 21, 2013 at 11:16 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 20/04/2013 20:42, Blue Swirl ha scritto:
>>> This is not entirely correct, I get these errors:
>>> mingw32:
>>> CC libfdt/fdt.o
>>> cc1: warnings being treated as errors
>>> /src/qemu/dtc/libfdt/fdt.c:1: warning: -fPIC ignored for target (all
>>> code is position independent)
>>>
>
> This is coming from the dtc makefile which explicitly passes in -fPIC
> via its default CFLAGS. I tried fixing by setting the Make invocation
> to replace CFLAGS entirely, which in effect removes the -fPIC: But I
> suffer a similar (later) failure to the one you posted below:
>
> LINK arm-softmmu/qemu-system-arm
> /usr/bin/ld: /home/peterc/Petalogix/Internal/plgx_src/qemu-build/dtc/libfdt/libfdt.a(fdt.o):
> relocation R_X86_64_32S against `.rodata' can not be used when making
> a shared object; recompile with -fPIC
> /home/peterc/Petalogix/Internal/plgx_src/qemu-build/dtc/libfdt/libfdt.a:
> could not read symbols: Bad value
>
> Looks like QEMU mandates that all static objects are -fPIC. A bit of
> googling suggests that this error is mingw specific in that mingw
> can't handle -fPIC.
Right, that's because QEMU is built as a position-independent executable.
PIE requirements actually are a bit less strict than -fPIC. Your
solution of passing the compilation flags sounds good, but do you pass
-Werror too?
Paolo
next prev parent reply other threads:[~2013-04-22 8:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 4:45 [Qemu-devel] [PATCH v5 0/3] DTC as submodule peter.crosthwaite
2013-04-18 4:46 ` [Qemu-devel] [PATCH v5 1/3] configure: Put cross compile flags in EXTRA_CFLAGS peter.crosthwaite
2013-04-18 4:46 ` [Qemu-devel] [PATCH v5 2/3] dtc: add submodule peter.crosthwaite
2013-04-18 4:47 ` [Qemu-devel] [PATCH v5 3/3] configure/Make: Build libfdt from submodule DTC peter.crosthwaite
2013-04-20 18:42 ` Blue Swirl
2013-04-21 13:16 ` Paolo Bonzini
2013-04-22 4:45 ` Peter Crosthwaite
2013-04-22 8:58 ` Paolo Bonzini [this message]
2013-05-24 14:16 ` Peter Maydell
2013-05-24 14:33 ` Edgar E. Iglesias
2013-05-24 14:34 ` Peter Maydell
2013-04-18 10:26 ` [Qemu-devel] [PATCH v5 0/3] DTC as submodule Edgar E. Iglesias
2013-04-18 11:02 ` Paolo Bonzini
2013-04-18 11:08 ` Edgar E. Iglesias
2013-04-18 11:10 ` Peter Maydell
2013-04-18 11:58 ` Edgar E. Iglesias
2013-04-18 11:12 ` Paolo Bonzini
2013-04-18 11:56 ` Edgar E. Iglesias
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=5174FBC3.30707@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).