From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Build errors on mainline kernel
Date: Fri, 9 Aug 2013 18:01:19 -0700 [thread overview]
Message-ID: <20130810010119.GA29407@us.ibm.com> (raw)
In-Reply-To: <EA801718-CA2E-4F85-AF6B-29119911038E@kernel.crashing.org>
Kumar Gala [galak@kernel.crashing.org] wrote:
|=20
| >=20
| > The pre-processor output for the first WARN_ON() is:
| >=20
| > ---
| > ({ int __ret_warn_on =3D !!(nr < 0 || nr >=3D 32); if (__builtin_consta=
nt_p(__ret_warn_on)) { if (__ret_warn_on) do { __asm__ __volatile__( "1: =
twi 31,0,0\n" ".section __bug_table,\"a\"\n" "2:\t" ".llong" " " "1b, %0\n=
" "\t.short %1, %2\n" ".org 2b+%3\n" ".previous\n" : : "i" ("/root/tmp/linu=
x.git/arch/powerpc/platforms/85xx/smp.c"), "i" (154), "i" (((1 << 0) | ((9)=
<< 8))), "i" (sizeof(struct bug_entry))); } while (0); } else { __asm__ __=
volatile__( "1: ""tdnei" " "" %4,0\n" ".section __bug_table,\"a\"\n"=
"2:\t" ".llong" " " "1b, %0\n" "\t.short %1, %2\n" ".org 2b+%3\n" ".previo=
us\n" : : "i" ("/root/tmp/linux.git/arch/powerpc/platforms/85xx/smp.c"), "i=
" (154), "i" (((1 << 0) | ((9) << 8))), "i" (sizeof(struct bug_entry)), "r"=
(__ret_warn_on)); } __builtin_expect(!!(__ret_warn_on), 0); });
| >=20
| > ---
| >=20
| >=20
| > Should I be doing something different to build with these configs ?
| >=20
|=20
| Hmm, that is odd.
|=20
| How about doing:
|=20
| $ make V=3D1
|=20
| so we can see what compiler flags are being passed around.
Sure.=20
make -f /root/tmp/linux.git/scripts/Makefile.build obj=3Darch/powerpc/platf=
orms/85xx arch/powerpc/platforms/85xx/smp.o
gcc -m64 -Wp,-MD,arch/powerpc/platforms/85xx/.smp.o.d -nostdinc -isystem=
/usr/lib/gcc/ppc64-redhat-linux/4.4.6/include -I/root/tmp/linux.git/arch/p=
owerpc/include -Iarch/powerpc/include/generated -I/root/tmp/linux.git/incl=
ude -Iinclude -I/root/tmp/linux.git/arch/powerpc/include/uapi -Iarch/powerp=
c/include/generated/uapi -I/root/tmp/linux.git/include/uapi -Iinclude/gener=
ated/uapi -include /root/tmp/linux.git/include/linux/kconfig.h -I/root/tmp=
/linux.git/arch/powerpc/platforms/85xx -Iarch/powerpc/platforms/85xx -D__KE=
RNEL__ -I/root/tmp/linux.git/arch/powerpc -Iarch/powerpc -Wall -Wundef -Ws=
trict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-im=
plicit-function-declaration -Wno-format-security -fno-delete-null-pointer-c=
hecks -O2 -msoft-float -pipe -I/root/tmp/linux.git/arch/powerpc -Iarch/pow=
erpc -mtraceback=3Dno -mcall-aixdesc -mcmodel=3Dmedium -mtune=3Dpower7 -mno=
-altivec -mno-vsx -mno-spe -mspe=3Dno -funit-at-a-time -fno-dwarf2-cfi-asm =
-mno-string -Wa,-me500 -Wframe-larger-than=3D2048 -fno-stack-protector -Wno=
-unused-but-set-variable -fomit-frame-pointer -Wdeclaration-after-statement=
-Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO=
-D"KBUILD_STR(s)=3D#s" -D"KBUILD_BASENAME=3DKBUILD_STR(smp)" -D"KBUILD=
_MODNAME=3DKBUILD_STR(smp)" -c -o arch/powerpc/platforms/85xx/.tmp_smp.o /r=
oot/tmp/linux.git/arch/powerpc/platforms/85xx/smp.c
{standard input}: Assembler messages:
{standard input}:244: Error: junk at end of line: `1'
make[2]: *** [arch/powerpc/platforms/85xx/smp.o] Error 1
make[1]: *** [arch/powerpc/platforms/85xx/smp.o] Error 2
make: *** [sub-make] Error 2
next prev parent reply other threads:[~2013-08-10 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 18:24 Build errors on mainline kernel Sukadev Bhattiprolu
2013-08-09 23:47 ` Kumar Gala
2013-08-10 1:01 ` Sukadev Bhattiprolu [this message]
[not found] ` <20130810010119.GA29407__43692.6458766267$1376096568$gmane$org@us.ibm.com>
2013-08-10 7:15 ` Andreas Schwab
2013-08-10 16:45 ` Sukadev Bhattiprolu
2013-08-10 17:47 ` Andreas Schwab
2013-08-12 5:42 ` Michael Ellerman
2013-08-12 6:02 ` Sukadev Bhattiprolu
2013-08-13 2:23 ` Michael Ellerman
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=20130810010119.GA29407@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.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;
as well as URLs for NNTP newsgroup(s).