All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Benoit <sab7@mail.ptd.net>
To: linux-kernel@vger.kernel.org
Subject: sparc 20 problem ver test9
Date: Mon, 10 Nov 2003 08:37:16 -0500	[thread overview]
Message-ID: <20031110083716.A32096@mail.ptd.net> (raw)

Hello,

System:
SPARC Station 20
Processor(s):
SuperSPARC II
Kernel: linux-2.6.0-test9
GCC: 2.95.3

1. make mrproper OK
2. make menuconfig OK
3. make


  CC      init/main.o
In file included from include/asm-generic/local.h:7,
                 from include/asm/local.h:4,
                 from include/linux/module.h:19,
                 from init/main.c:15:
include/asm/hardirq.h: In function `irqs_running':
include/asm/hardirq.h:134: `smp_num_cpus' undeclared (first use in this function)
include/asm/hardirq.h:134: (Each undeclared identifier is reported only once
include/asm/hardirq.h:134: for each function it appears in.)
include/asm/hardirq.h:135: `__brlock_array' undeclared (first use in this function)
include/asm/hardirq.h:135: `BR_GLOBALIRQ_LOCK' undeclared (first use in this function)
include/asm/hardirq.h: In function `release_irqlock':
include/asm/hardirq.h:147: warning: implicit declaration of function `br_write_unlock'
include/asm/hardirq.h:147: `BR_GLOBALIRQ_LOCK' undeclared (first use in this function)
In file included from init/main.c:33:
include/linux/kernel_stat.h: In function `kstat_irqs':
include/linux/kernel_stat.h:47: warning: implicit declaration of function `cpu_possible'
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2

shouldn't this be pointing to:

include/asm-sparc/hardirg.h  ???


Thanks,


-- 
Stan Benoit<sab7@mail.ptd.net>
Mondo Dev/Testing 
http://www.mondorescue.org
Testing:
http://www.nakedsoul.org/~troff


             reply	other threads:[~2003-11-10 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 13:37 Stan Benoit [this message]
2003-11-10 15:33 ` sparc 20 problem ver test9 Christian
2003-11-10 15:48 ` Rob Radez
2003-11-12 10:51   ` David J. M. Karlsen

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=20031110083716.A32096@mail.ptd.net \
    --to=sab7@mail.ptd.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.