All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] fix build failure w. gcc-4.3.3
Date: Sat, 31 Jan 2009 17:53:06 +0000	[thread overview]
Message-ID: <20090131185306.6ab017eb@scarran.roarinelk.net> (raw)
In-Reply-To: <20090130102854.GA13640@roarinelk.homelinux.net>

On Sat, 31 Jan 2009 12:35:21 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> On Saturday 31 January 2009 12:13:26 Manuel Lauss wrote:
> > On Sat, 31 Jan 2009 11:56:05 -0500 Mike Frysinger wrote:
> > > On Saturday 31 January 2009 03:46:05 Manuel Lauss wrote:
> > > > On Fri, 30 Jan 2009 11:28:54 +0100 Manuel Lauss 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.
> >
> > Well, at least here -Wno-format-security doesn't work, neither on x86,
> > sh nor mips.  Otherwise I would have sent a patch doing exactly that.
> 
> works fine for me.  not that it matters as the kernel already can handle this:
> KBUILD_CFLAGS += $(call cc-option,-Wno-format-security,)

I was beginning to suspect something bad on my end.
 
> also, this isnt a Gentoo specific issue.  other distros are enabling this flag 
> by default as well.  they just dont make cross-compiler generation as easy as 
> Gentoo ;).
> -mike

That's why I like Gentoo so much ;-)

In any case, I rebuilt all compilers without this patch so it's no
longer a concern for me.

Thanks Mike,
	Manuel Lauss

      parent reply	other threads:[~2009-01-31 17:53 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
2009-01-31 17:13 ` Manuel Lauss
2009-01-31 17:35 ` Mike Frysinger
2009-01-31 17:53 ` Manuel Lauss [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=20090131185306.6ab017eb@scarran.roarinelk.net \
    --to=mano@roarinelk.homelinux.net \
    --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 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.