On Sat, 29 Jul 2006 21:19:38 +0200, Adrian Bunk said: > That was never true in Arjan's patches. > > The only change is from a gcc version check to a feature check. > > In both cases, a gcc 4.1 without the appropriate patch applied will > result in this option not being set. What do you get if you have a gcc 4.1.1. that has the stack protector option (so a feature check works), but not the fix for gcc PR 28281?
Attachment:
pgpN7XTb6B78d.pgp
Description: PGP signature
- Follow-Ups:
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Arjan van de Ven <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Adrian Bunk <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- References:
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Andi Kleen <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Adrian Bunk <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Andi Kleen <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- From: Adrian Bunk <[email protected]>
- Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- Prev by Date: Re: [PATCH for 2.6.18] [8/8] MM: Remove rogue readahead printk
- Next by Date: Re: Building the kernel on an SMP box?
- Previous by thread: Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- Next by thread: Re: [patch 2/5] Add the Kconfig option for the stackprotector feature
- Index(es):
 |