qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: Problems encountered while building qemu-0.6.1


From: Peter S. Mazinger
Subject: [Qemu-devel] Re: Problems encountered while building qemu-0.6.1
Date: Tue, 22 Feb 2005 13:04:17 +0100 (CET)

On Tue, 22 Feb 2005, Peter S. Mazinger wrote:

> On Sun, 20 Feb 2005, Peter S. Mazinger wrote:
> 
> I have attached 2 patches showing what is needed (and commented the 
> errors) building w/ gcc-3.3.5 and gcc-3.4.3 (the only diff is building 
> op_helper.o fails w/ gcc-3.3.5)
> 
> I can help w/ the ssp (stack-protector) tests, if noone has such gcc, the 
> -fno-pic failure can be easily "simulated" replacing -fno-pic with -fPIC.
> 
> The tests were done w/ latest cvs (20050221)
> The attached patches allow building qemu, but do not remove the text 
> relocations (probably produced by using -fno-pic)

the relocation types not recognized by dyngen are
R_386_GOT32/R_386_GOTOFF/R_386_GOTPC/R_386_PLT32

Peter
> 
> > 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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]