public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Kernel 3.10-rc1 build warning on 32-bit ppc associated with commit 3925f46
Date: Tue, 14 May 2013 10:29:16 -0500	[thread overview]
Message-ID: <5192584C.1060003@lwfinger.net> (raw)

Hi,

When building 3.10-rc1 on a PowerBook G4, I get the following warning:

cc1: warnings being treated as errors
arch/powerpc/perf/core-book3s.c: In function ‘power_pmu_bhrb_read’:
arch/powerpc/perf/core-book3s.c:1479: error: integer constant is too large for 
‘long’ type
make[2]: *** [arch/powerpc/perf/core-book3s.o] Error 1
make[1]: *** [arch/powerpc/perf] Error 2
make[1]: *** Waiting for unfinished jobs....
   LD      arch/powerpc/platforms/powermac/built-in.o
   LD      arch/powerpc/platforms/built-in.o
make[1]: Leaving directory `/home/finger/wireless-testing'
make: *** [debian/stamp/build/kernel] Error 2

The code in question came from commit 3925f46 entitled "powerpc/perf: Enable 
branch stack sampling framework". The gcc version is 4.4.5 running with a Mint 9 
distribution.

I have disabled the "-Werror" switch so that the build can continue. That 
Kconfig question about disabling WERROR is a bit confusing with its double 
negative construction.

Thanks,

Larry

             reply	other threads:[~2013-05-14 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 15:29 Larry Finger [this message]
2013-05-14 23:33 ` Kernel 3.10-rc1 build warning on 32-bit ppc associated with commit 3925f46 Benjamin Herrenschmidt
2013-05-15  3:07   ` Larry Finger

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=5192584C.1060003@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=benh@kernel.crashing.org \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@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