All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Jones <sjones@ossm.edu>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SPARC include problem
Date: Tue, 08 May 2001 22:17:35 -0500	[thread overview]
Message-ID: <3AF8B6CF.94EF38D@ossm.edu> (raw)
In-Reply-To: <3AF71B1F.56FFCA16@ossm.edu> <20010508120108.A1802@arthur.ubicom.tudelft.nl>

The include error was in kernel/sched.c . Should I rewrite the includes
for this file to include include/asm/irq.h over include/linux/irq.h? I
temporarily bypassed this problem by creating a blank asm/hw_irq.h . 

I also ran into a compile problem in arch/sparc/kernel/sparc_ksyms.c .
The rw semaphores seem to be undeclared. Here are the warnings:

D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -m32 -pipe -mno-fpu
-fcall-used-g5 -fcall-used-g7    -DEXPORT_SYMTAB -c sparc_ksyms.c
In file included from /usr/src/linux-2.4.4/include/linux/sched.h:9,
                 from sparc_ksyms.c:17:
/usr/src/linux-2.4.4/include/linux/binfmts.h:45: warning: `struct
mm_struct' declared inside parameter list
/usr/src/linux-2.4.4/include/linux/binfmts.h:45: warning: its scope is
only this definition or declaration, which is probably not what you
want.
sparc_ksyms.c:121: `___down_read' undeclared here (not in a function)
sparc_ksyms.c:121: initializer element is not constant
sparc_ksyms.c:121: (near initialization for
`__ksymtab____down_read.value')
sparc_ksyms.c:122: `___down_write' undeclared here (not in a function)
sparc_ksyms.c:122: initializer element is not constant
sparc_ksyms.c:122: (near initialization for
`__ksymtab____down_write.value')
sparc_ksyms.c:123: `___up_read' undeclared here (not in a function)
sparc_ksyms.c:123: initializer element is not constant
sparc_ksyms.c:123: (near initialization for
`__ksymtab____up_read.value')
sparc_ksyms.c:124: `___up_write' undeclared here (not in a function)
sparc_ksyms.c:124: initializer element is not constant
sparc_ksyms.c:124: (near initialization for
`__ksymtab____up_write.value')
make[1]: *** [sparc_ksyms.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.4/arch/sparc/kernel'
make: *** [_dir_arch/sparc/kernel] Error 2

Thank you,

Sean


Erik Mouw wrote:
> 
> On Mon, May 07, 2001 at 05:01:03PM -0500, Sean Jones wrote:
> > In compiling 2.4.4-ac5 for my SPARCStation 20, I had an error in the
> > compile resulting from the inability to find a hw_irq.h in the
> > include/asm directory. Do you know where I may be able to find such a
> > file?
> 
> You don't. I discussed this last week with Russell King: the ARM port
> also doesn't have the file hw_irq.h in include/asm-arm. According to
> Russell it is only needed in the arch dependent subdirectories, and not
> in the drivers.
> 
> Any driver that includes linux/irq.h is not written to be portable. The
> only generic driver that includes it is driver/pcmcia/hd64465_ss.c, but
> on second glance it's a Hitachi HD64465 specific driver anyway.
> 
> Erik
> 
> --
> J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
> of Electrical Engineering, Faculty of Information Technology and Systems,
> Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
> Phone: +31-15-2783635  Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
> WWW: http://www-ict.its.tudelft.nl/~erik/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-05-09  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-07 22:01 SPARC include problem Sean Jones
2001-05-07 22:53 ` David S. Miller
     [not found]   ` <3AF72F44.27D752D3@ossm.edu>
2001-05-08  0:54     ` Sean Jones
2001-05-08 10:01 ` Erik Mouw
2001-05-09  3:17   ` Sean Jones [this message]
2001-05-09  8:27     ` Erik Mouw

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=3AF8B6CF.94EF38D@ossm.edu \
    --to=sjones@ossm.edu \
    --cc=J.A.K.Mouw@ITS.TUDelft.NL \
    --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.