From: Giuliano Pochini <pochini@shiny.it>
To: LinuxPPC-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Can't compile 2.6.7 with gcc 3.4.1
Date: Mon, 26 Jul 2004 22:38:32 +0200 [thread overview]
Message-ID: <20040726223832.3edafe0a.pochini@shiny.it> (raw)
Is this a known problem ? I can't compile the kernel 2.6.7 with gcc 3.4.1:
CC arch/ppc/kernel/traps.o
arch/ppc/kernel/traps.c: In function `AltivecUnavailException':
arch/ppc/kernel/traps.c:650: warning: unsigned int format, long unsigned int arg (arg 3)
arch/ppc/kernel/traps.c: In function `AltivecAssistException':
arch/ppc/kernel/traps.c:665: warning: implicit declaration of function `emulate_altivec'
CC arch/ppc/kernel/irq.o
CC arch/ppc/kernel/idle.o
CC arch/ppc/kernel/time.o
{standard input}: Assembler messages:
{standard input}:161: Error: Unrecognized opcode: `mftb'
{standard input}:393: Error: Unrecognized opcode: `mftb'
{standard input}:538: Error: Unrecognized opcode: `mftb'
{standard input}:728: Error: Unrecognized opcode: `mftb'
{standard input}:839: Error: Unrecognized opcode: `mftb'
{standard input}:1054: Error: Unrecognized opcode: `mftbu'
{standard input}:1055: Error: Unrecognized opcode: `mftb'
{standard input}:1056: Error: Unrecognized opcode: `mftbu'
make[1]: *** [arch/ppc/kernel/time.o] Error 1
make: *** [arch/ppc/kernel] Error 2
[root@Jay linux-2.6.7]#
I have no problems with gcc 3.3.3.
(dual-G4 MDD)
--
Giuliano.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-07-26 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 20:38 Giuliano Pochini [this message]
2004-07-26 23:02 ` Can't compile 2.6.7 with gcc 3.4.1 Christian Kujau
2004-07-28 7:22 ` Giuliano Pochini
2004-07-27 17:47 ` Tom Rini
2004-07-28 6:24 ` Olaf Hering
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=20040726223832.3edafe0a.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).