From: Giuseppe Coviello <cjg@cruxppc.org>
To: linuxppc-dev@ozlabs.org
Subject: Fail building 2.6.31.x for CHRP using gcc-4.4.x
Date: Sun, 1 Nov 2009 10:17:00 +0100 [thread overview]
Message-ID: <a265241c0911010117m65335b80g94457a07d0610cbe@mail.gmail.com> (raw)
Hi, we are having trouble while building kernel 2.6.31.x and also
2.6.32rc for CHRP platforms using gcc-4.4.x, the error that give us
the compilation is:
CC arch/powerpc/sysdev/indirect_pci.o
CC arch/powerpc/sysdev/i8259.o
LD arch/powerpc/sysdev/built-in.o
CC arch/powerpc/platforms/chrp/setup.o
cc1: warnings being treated as errors
arch/powerpc/platforms/chrp/setup.c: In function 'chrp_event_scan':
arch/powerpc/platforms/chrp/setup.c:378: error: the frame size of 1040
bytes is larger than 1024 bytes
make[2]: *** [arch/powerpc/platforms/chrp/setup.o] Error 1
make[1]: *** [arch/powerpc/platforms/chrp] Error 2
make: *** [arch/powerpc/platforms] Error
The same kernel, with the same configuration builds fine using gcc-4.3.x.
Regards, Giuseppe
next reply other threads:[~2009-11-01 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 9:17 Giuseppe Coviello [this message]
2009-11-01 11:41 ` Fail building 2.6.31.x for CHRP using gcc-4.4.x Stephen Rothwell
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=a265241c0911010117m65335b80g94457a07d0610cbe@mail.gmail.com \
--to=cjg@cruxppc.org \
--cc=linuxppc-dev@ozlabs.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