public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] fix build failure w. gcc-4.3.3
Date: Sat, 31 Jan 2009 16:56:05 +0000	[thread overview]
Message-ID: <200901311156.06604.vapier@gentoo.org> (raw)
In-Reply-To: <20090130102854.GA13640@roarinelk.homelinux.net>

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

On Saturday 31 January 2009 03:46:05 Manuel Lauss wrote:
> On Fri, 30 Jan 2009 11:28:54 +0100
>
> Manuel Lauss <mano@roarinelk.homelinux.net> wrote:
> > gcc-4.3.3 likes to have printf() and related functions to have
> > at least 2 arguments when the format string is not a constant:
> >
> > cc1: warnings being treated as error
> > arch/sh/kernel/setup.c: In function 'early_parse_mem':
> > arch/sh/kernel/setup.c:111: error: format not a string literal and no
> > format arguments
>
> Please disregard this patch:  turns out that Gentoo applied a patch
> which unconditionally enables -Wformat-security and produces this
> message.

that's incorrect.  the patch sets format-security on by default, not 
unconditionally.  having the common kernel itself build with -Wno-format-
security probably is worthwhile.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2009-01-31 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 10:28 [PATCH] fix build failure w. gcc-4.3.3 Manuel Lauss
2009-01-31  8:46 ` Manuel Lauss
2009-01-31 16:56 ` Mike Frysinger [this message]
2009-01-31 17:13 ` Manuel Lauss
2009-01-31 17:35 ` Mike Frysinger
2009-01-31 17:53 ` Manuel Lauss

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=200901311156.06604.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=linux-sh@vger.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