From: John Mylchreest <johnm@gentoo.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Olaf Hering <olh@suse.de>,
linux-kernel@vger.kernel.org, stable@kernel.org,
paulus@samba.org
Subject: Re: [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16
Date: Sun, 2 Apr 2006 16:22:49 +0100 [thread overview]
Message-ID: <20060402152249.GD3443@getafix.willow.local> (raw)
In-Reply-To: <1143989378.2994.25.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
On Sun, Apr 02, 2006 at 04:49:37PM +0200, Arjan van de Ven <arjan@infradead.org> wrote:
> 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 <arjan@infradead.org> 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
Yeah, something which I completely disregarded without thinking about
until this thread. Always helps not looking at this at 1am ;)
I always thought the arch/boot code should stay as part of the kernel
build. I'll re-address :)
Cheers for the input.
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-04-02 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 22:48 [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16 John Mylchreest
2006-04-02 8:58 ` Olaf Hering
2006-04-02 10:22 ` John Mylchreest
2006-04-02 10:28 ` Olaf Hering
2006-04-02 10:58 ` John Mylchreest
2006-04-02 11:10 ` Olaf Hering
2006-04-02 11:20 ` John Mylchreest
2006-04-02 11:42 ` Olaf Hering
2006-04-04 8:57 ` John Mylchreest
2006-04-04 9:41 ` Olaf Hering
2006-04-04 10:01 ` John Mylchreest
2006-04-04 10:58 ` Olaf Hering
2006-04-10 9:01 ` John Mylchreest
2006-04-02 13:15 ` Arjan van de Ven
2006-04-02 13:56 ` John Mylchreest
2006-04-02 14:01 ` Olaf Hering
2006-04-02 14:35 ` John Mylchreest
2006-04-02 14:49 ` Arjan van de Ven
2006-04-02 15:22 ` John Mylchreest [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060402152249.GD3443@getafix.willow.local \
--to=johnm@gentoo.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=paulus@samba.org \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.