From: John Mylchreest <johnm@gentoo.org>
To: Olaf Hering <olh@suse.de>
Cc: 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: Mon, 10 Apr 2006 09:01:45 +0000 [thread overview]
Message-ID: <20060410090145.GB16413@getafix.willow.local> (raw)
In-Reply-To: <20060404105826.GA22820@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On Tue, Apr 04, 2006 at 12:58:26PM +0200, Olaf Hering <olh@suse.de> wrote:
> On Tue, Apr 04, John Mylchreest wrote:
>
> > On Tue, Apr 04, 2006 at 11:41:24AM +0200, Olaf Hering <olh@suse.de> wrote:
> > > I think this should go into the main makefile, HOSTCFLAGS or similar. If
> > > you look around quickly in the gentoo bugzilla, all non-userland
> > > packages (grub, xen, kernel etc.) require the -fno-feature.
> >
> > I'm not completely sure I understand where you are coming from here?
> > I assume you mean adding -fno-stack-protector to the host userlands
> > CFLAGS variable (or similar) to make it a global change, but if so
> > you're missing my point.
>
> I mean the whole kernel should be compiled with it, if you put it into
> global cflags, the boot parts will pick it up from there.
Sorry, for the belated reply. I thought that might be what you refered to,
however I think this is going to cause additional problems. The powerpc
code which is effected uses the CROSS32CC which may, or may not be the
same compiler as used by the host cc. This means that it could also have
different capabilities, and the worst scenario in this specific
situation would be where the hostcc didn't support ssp, but the
cross32cc did, and had it enforced.
I don't think this is the right approach, and keeping it isolated to the
boot code makes more sense to me.
--
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 --]
next prev parent reply other threads:[~2006-04-10 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 22:48 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 [this message]
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
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=20060410090145.GB16413@getafix.willow.local \
--to=johnm@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®