From: Dave Jones <davej@suse.de>
To: Nathan <wfilardo@fuse.net>, rml@tech9.net
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Various issues with 2.5.2-dj6
Date: Fri, 1 Feb 2002 02:34:07 +0100 [thread overview]
Message-ID: <20020201023407.K10343@suse.de> (raw)
In-Reply-To: <3C58B3DD.3000800@fuse.net> <20020131041901.H31313@suse.de> <3C59BA94.1050307@fuse.net>
In-Reply-To: <3C59BA94.1050307@fuse.net>; from wfilardo@fuse.net on Thu, Jan 31, 2002 at 04:43:48PM -0500
On Thu, Jan 31, 2002 at 04:43:48PM -0500, Nathan wrote:
> > > Issue 2: Two IEEE1934 modules needed to have "#include
> > > <linux/interrupt.h>" added (host.c and another one I forget)
> > Can you send the gcc error messages of these ?
> > (A patch would be nice too)
> >
> GCC error messages:
>
> gcc -D__KERNEL__
> -I/home/expsoft/src/linux-kernel/linux-2.5/linux/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686 -DMODULE -DMODVERSIONS -include
> /home/expsoft/src/linux-kernel/linux-2.5/linux/include/linux/modversions.h
> -DKBUILD_BASENAME=hosts -c
> -o hosts.o hosts.c
> hosts.c: In function `hpsb_ref_host_Rsmp_b2d7a7ae':
> hosts.c:53: `current' undeclared (first use in this function)
> hosts.c:53: (Each undeclared identifier is reported only once
> hosts.c:53: for each function it appears in.)
> hosts.c:63: warning: implicit declaration of function
> `preempt_schedule_Rsmp_707f93dd'
Looks like another preempt problem to me, as hosts.c doesn't
reference current in my tree fwics. The error on line 63
looks suspect too.
You may also get away with include sched.h instead of interrupt.h
(which indirectly includes sched.h amongst other things).
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-02-01 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 3:02 Various issues with 2.5.2-dj6 Nathan
2002-01-31 3:19 ` Dave Jones
2002-01-31 3:32 ` Robert Love
2002-01-31 3:56 ` Greg KH
2002-01-31 9:04 ` Vojtech Pavlik
2002-01-31 21:43 ` Nathan
2002-02-01 1:34 ` Dave Jones [this message]
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=20020201023407.K10343@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=wfilardo@fuse.net \
/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