On Sun, 2006-04-02 at 14:56 +0100, John Mylchreest wrote:
> On Sun, Apr 02, 2006 at 03:15:38PM +0200, Arjan van de Ven <[email protected]> wrote:
> >
> > > 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..
>
> It gets turned on elsewhere (gcc spec),
ehh???
so you change gcc to force a specific, non-standard option on, and
something breaks as a result... better get the gcc spec fixed I'd say
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
