From: "Peter S. Mazinger" <ps.m@gmx.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Problems encountered while building qemu-0.6.1
Date: Sun, 20 Feb 2005 16:45:02 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0502201642300.2930-100000@lnx.bridge.intra> (raw)
In-Reply-To: <Pine.LNX.4.44.0502201540060.2930-100000@lnx.bridge.intra>
On Sun, 20 Feb 2005, Peter S. Mazinger wrote:
for current cvs almost everything applies, some changes though.
> Hello!
>
> 1. CFLAGS/LDFLAGS from config-host.mak are overwritten/ignored
> 2. VL_LDFLAGS/OP_CFLAGS should also "inherit" from config-host.mak
> 3. Trying to build qemu in an environment, where gcc defaults to -fPIC
> fails building op.o/osdep.o/helper.o.
only op.o/helper.o fail.
> If I disable -fPIC on the complete build, the resulting qemu-* files
> contain text relocations (readelf -d <file>). Due to the fact that they
> are like shared libs, the text relocs should not be present.
> 4. The files qemu-* (user and sofmmu) are created w/ LDFLAGS=-Wl,-shared
> creting ET_DYN/PIE executables. gcc-3.4 and binutils-2.15 support gcc
> -pie/ld -pie, this can be checked by gcc -fpie and ld --help | grep pie
> 5. building qemu w/ a propolice/ssp patched gcc, op.o creation fails if
> -fstack-protector-all is enabled.
if op.o is built w/ -fstack-protector, it fails creating op.h
>
> Please CC to me, I am not subscribed, thanks.
>
> Peter
>
>
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
next prev parent reply other threads:[~2005-02-20 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 14:59 [Qemu-devel] Problems encountered while building qemu-0.6.1 Peter S. Mazinger
2005-02-20 15:45 ` Peter S. Mazinger [this message]
2005-02-22 11:21 ` [Qemu-devel] " Peter S. Mazinger
2005-02-22 12:04 ` Peter S. Mazinger
2005-02-22 15:33 ` Peter S. Mazinger
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=Pine.LNX.4.44.0502201642300.2930-100000@lnx.bridge.intra \
--to=ps.m@gmx.net \
--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).