From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: linuxppc-dev@ozlabs.org, kamalesh@linux.vnet.ibm.com,
sam@ravnborg.org, linux-kernel@vger.kernel.org,
balbir@linux.vnet.ibm.com
Subject: Re: 2.6.24-rc1-git15 Kernel build fails on powerpc - Unrecognized opcode: `dssall'
Date: Tue, 06 Nov 2007 03:10:01 -0800 (PST) [thread overview]
Message-ID: <20071106.031001.189578769.davem@davemloft.net> (raw)
In-Reply-To: <1194346486.4066.13.camel@johannes.berg>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 06 Nov 2007 11:54:46 +0100
>
>
> > > CHK include/linux/compile.h
> > > AS arch/powerpc/kernel/swsusp_32.o
> > > arch/powerpc/kernel/swsusp_32.S: Assembler messages:
> > > arch/powerpc/kernel/swsusp_32.S:138: Error: Unrecognized opcode: `dssall'
> > > make[1]: *** [arch/powerpc/kernel/swsusp_32.o] Error 1
> > > make: *** [arch/powerpc/kernel] Error 2
> > >
> >
> > Looks suspiciously like an altivec issue. Could you compile with make
> > V=1 and/or do a git bisect and see what broke?
>
> Looks more like a toolchain issue to me.
Or, this is another instance of the "CFLAGS environment variable"
problem.
For a few days, the kbuild stuff would integrate any CFLAGS,
AFLAGS, etc. settings you might have set in your environment.
next prev parent reply other threads:[~2007-11-06 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 10:34 2.6.24-rc1-git15 Kernel build fails on powerpc - Unrecognized opcode: `dssall' Kamalesh Babulal
2007-11-06 10:46 ` Balbir Singh
2007-11-06 10:54 ` Johannes Berg
2007-11-06 11:10 ` David Miller [this message]
2007-11-06 11:28 ` Kamalesh Babulal
2007-11-06 13:39 ` Balbir Singh
2007-11-06 15:44 ` Andy Whitcroft
2007-11-07 9:38 ` Johannes Berg
2007-11-07 12:49 ` Johannes Berg
2007-11-07 12:59 ` [PATCH] powerpc swsusp: make altivec code depend on CONFIG_ALTIVEC Johannes Berg
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=20071106.031001.189578769.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=balbir@linux.vnet.ibm.com \
--cc=johannes@sipsolutions.net \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam@ravnborg.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).