![]() | |||||||||||||
Messages in this thread |
> Going from that, I can push a patch for gcc upstream to remove the > __KERNEL__ dep, but gcc4.1 ships with ssp by standard, and the semantics > between the IBM patch for SSP applied to gcc-3 and ggc-4 have changed. > > -fno-stack-protector would work for gcc4, but for gcc3 it could still be since this is a thing you have to turn on to get it, not off to not get it, I think you're missing something big here ;) > patially enabled, and requires -fno-stack-protector-all. Mind If I ask > whats incorrect about defining __KERNEL__ for the bootcflags? it's silly and it's a non-standard gcc ... better get the gcc fixed to at least have the upstream protocol of having to turn it on not off.. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-04-03 14:38 [from the cache] ©2003-2008 | |||||||||||||