1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Maurice van der Pot wrote: |
5 |
> On Tue, Apr 12, 2005 at 12:10:25PM -0400, Daniel Ostrow wrote: |
6 |
> |
7 |
>>Take a look at dev-libs/glib/files/glib-2.6.3-testglib-ssp.patch to see |
8 |
>>how solar and I dealt with a similar issue with tests and ssp. See if |
9 |
>>you can adapt it, we just forced -fno-stack-protector after the CFLAGS |
10 |
>>pulled in from the system. |
11 |
>> |
12 |
> |
13 |
> |
14 |
> Ok, so I thought it was all well and good, but now a bug report made me |
15 |
> realise that gcc < 3.4 doesn't have -fpie/-fno-pie. |
16 |
> |
17 |
> Here's the problem: |
18 |
> 1) valgrind has some features that only work with -fpie |
19 |
> 2) valgrind's tests fail to build with -fpie |
20 |
> 3) because of the hardened gcc profile, valgrind's tests need -fno-pie |
21 |
> 4) simply patching some makefiles to add -fno-pie for tests is not |
22 |
> possible because gcc < 3.4 doesn't support -fno-pie |
23 |
> 5) having the valgrind developers modify their configure/makefiles to |
24 |
> add -fno-pie for tests in case gcc supports it is not enough, because |
25 |
> user CFLAGS are appended and CFLAGS in make.conf may contain -fpie |
26 |
> 6) using filter-flags to get rid of -fpie in user's CFLAGS actually |
27 |
> adds -fno-pie and disables features referred to in 1) |
28 |
> |
29 |
> What do I do now? |
30 |
> |
31 |
> Why is -fno-pie being added by filter-flags anyway? |
32 |
> |
33 |
> Maurice. |
34 |
> |
35 |
Sorry for the dumb question but was do -fpie and -fno-pie do? |
36 |
|
37 |
Vibhav |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v1.4.1 (GNU/Linux) |
40 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
41 |
|
42 |
iD8DBQFCYCCDiriTCkdDSX4RAh0jAKCUE560f+O4wDPLsG4cKQvYAPIb/wCfZoaE |
43 |
wom30rnS7jvQRshUsIDCyGc= |
44 |
=Wnty |
45 |
-----END PGP SIGNATURE----- |
46 |
-- |
47 |
gentoo-dev@g.o mailing list |