Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-mips@linux-mips.org
Subject: Re: [SOLVED] Re: GCC-4.3.3 sillyness
Date: Wed, 25 Feb 2009 21:48:48 -0500	[thread overview]
Message-ID: <49A60310.9030900@gentoo.org> (raw)
In-Reply-To: <49A4D370.3080300@gentoo.org>

Kumba wrote:
> 
> Yeah, I did some digging and it looks like we added a patch called 
> "10_all_gcc-default-format-security.patch" into our gcc-4.3.3 ebuild.  
> The patch claims it was ripped from Debian; can any Debian devs comment 
> on whether you guys still use this patch and what the idea behind it 
> is?  I'm not sure if I'll find any discussion on our end as to why it's 
> included without finding Mike (vapier) around.

Looks like Gentoo and Debian aren't alone.  This was discussed on lkml because 
other mainstream distros are enabling it as a default as well, so the proposed 
solution is to just disable the format check in the kernel:

http://lkml.org/lkml/2009/2/4/259

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org

"The past tempts us, the present confuses us, the future frightens us.  And our 
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

      reply	other threads:[~2009-02-26  2:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  7:44 GCC-4.3.3 sillyness Manuel Lauss
2009-01-30  8:23 ` Geert Uytterhoeven
2009-01-30  8:55   ` Manuel Lauss
2009-01-30 14:03 ` Ralf Baechle
2009-01-30 16:56   ` Manuel Lauss
2009-01-31  7:59 ` [SOLVED] " Manuel Lauss
2009-02-25  5:13   ` Kumba
2009-02-26  2:48     ` Kumba [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=49A60310.9030900@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    --cc=ralf@linux-mips.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