On Sat, Jan 03, 2009 at 07:52:10PM +0100, Stefan Reimer wrote:
On Fri, Jan 02, 2009 at 11:14:52PM +0100, Stefan Reimer wrote:
I am using gentoo hardened:
gcc (Gentoo Hardened 4.3.2-r7 p1.5, ssp, fortify, pie-10.2.0) 4.3.2
glibc 2.8
Using gcc -v gives:
/usr/libexec/gcc/x86_64-pc-linux-gnu/4.3.2/cc1 -quiet -v -I. -I. -I../include -I../include -imultilib 32 preloader.c -D_FORTIFY_SOURCE=2
-fPIE -fstack-protector -fstack-protector-all -fno-strict-overflow -quiet
-dumpbase preloader.c -m32 -march=athlon64 -auxbase-strip preloader.o -O2 -Wall -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits
-Wpointer-arith -version -fno-strict-aliasing -o - |
/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../x86_64-pc-linux-gnu/bin/as
-V -Qy --32 -o preloader.o -
The hardened gcc specs brings in -fPIE, which is similiar to -fPIC.
So YES I do ;-)
Is this a problem ?
-fPIE is a bit useless for the preloader (wine-preloader is actually
loaded at a fixed
address), but it should not fail to build I guess.
Does Wine still work afterwards?
I don't see the patch hurting anything though.
Ciao, Marcus
Hi, -fPIE is introduced by using the gentoo hardened profile and is applied everywhere possible. I think wine should be able to be build with -fPIE, despite not improving security be any means.
Wine works like a charm btw.
Sry for the double postings!
Cyas Stefan
-
Stefan Reimer