public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
	Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
Subject: Re: Build error : 2.6.21-rc6-mm1 on sparc64
Date: Tue, 10 Apr 2007 18:18:54 -0700	[thread overview]
Message-ID: <20070410181854.7d532c59.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070411004838.GD15262@Krystal>

On Tue, 10 Apr 2007 20:48:38 -0400
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:

> I get the following build error when building 2.6.21-rc6-mm1 for
> sparc64:
> 
>   /opt/crosstool/gcc-3.4.5-glibc-2.3.6/sparc64-unknown-linux-gnu/bin/sparc64-unknown-linux-gnu-gcc -Wp,-MD,arch/sparc64/kernel/.traps.o.d  -nostdinc -isystem /opt/crosstool/gcc-3.4.5-glibc-2.3.6/sparc64-unknown-linux-gnu/lib/gcc/sparc64-unknown-linux-gnu/3.4.5/include -D__KERNEL__ -Iinclude -Iinclude2 -I/home/compudj/git/linux-2.6-lttng/include -include include/linux/autoconf.h -I/home/compudj/git/linux-2.6-lttng/arch/sparc64/kernel -Iarch/sparc64/kernel -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Os -m64 -pipe -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -ffixed-g5 -fcall-used-g7 -Wno-sign-compare -Wa,--undeclared-regs -fomit-frame-pointer -Wdeclaration-after-statement -Werror  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(traps)"  -D"KBUILD_MODNAME=KBUILD_STR(traps)" -c -o arch/sparc64/kernel/traps.o /home/compudj/git/linux-2.6-lttng/arch/sparc64/kernel/traps.c
> /home/compudj/git/linux-2.6-lttng/arch/sparc64/kernel/traps.c: In function `init_cur_cpu_trap':
> /home/compudj/git/linux-2.6-lttng/arch/sparc64/kernel/traps.c:2497: warning: implicit declaration of function `hard_smp_processor_id'
> make[2]: *** [arch/sparc64/kernel/traps.o] Error 1
> make[1]: *** [arch/sparc64/kernel] Error 2
> make: *** [_all] Error 2

Not sure what the approved fix is here.  Fernando, please take a look, and
review all other architectures?


  reply	other threads:[~2007-04-11  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11  0:48 Build error : 2.6.21-rc6-mm1 on sparc64 Mathieu Desnoyers
2007-04-11  1:18 ` Andrew Morton [this message]
2007-04-11  2:15   ` Fernando Luis Vázquez Cao
2007-04-11  2:34     ` Andrew Morton
2007-04-11  2:41       ` Mathieu Desnoyers

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=20070410181854.7d532c59.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=sparclinux@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