From: "George P Nychis" <gnychis@cmu.edu>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: 2.4.32: unresolved symbol unregister_qdisc
Date: Sun, 9 Apr 2006 13:37:25 -0400 (EDT) [thread overview]
Message-ID: <1786.128.2.140.234.1144604245.squirrel@128.2.140.234> (raw)
In-Reply-To: <20060408163743.c59d6e59.rdunlap@xenotime.net>
Thanks for the help.
Here is the makefile:
http://rafb.net/paste/results/auchPH75.html
And here is the full errors I receive:
http://rafb.net/paste/results/Qplpqw74.html
Greatly appreciate it
- George
> On Sat, 8 Apr 2006 19:18:47 -0400 (EDT) George P Nychis wrote:
>
>> Yeah, this module is unfortunately not under the GPL, it was made for
>> research and i am not the author, I was only given the code for my own
>> research.
>>
>> I enabled that support in the kernel, and then tried to recompile and
>> get tons of errors/warnings... so maybe I am missing something else to
>> be enabled in the kernel... here are a few examples of errors:
>> /usr/include/linux/skbuff.h:30:26: net/checksum.h: No such file or
>> directory /usr/include/asm/irq.h:16:25: irq_vectors.h: No such file or
>> directory /usr/include/linux/irq.h:72: error: `NR_IRQS' undeclared here
>> (not in a function) /usr/include/asm/hw_irq.h:28: error:
>> `NR_IRQ_VECTORS' undeclared here (not in a function)
>>
>> I think those are the top most errors, so if i can fix those hopefully
>> the rest shall vanish!
>
> Looks like a Makefile problem then. Can you post the Makefile? Hopefully
> it is using a Makefile and not just an elaborate gcc command line.
>
> [and please don't top-post]
>
>> - George
>>
>>
>>> From: "George P Nychis" <gnychis@cmu.edu> Date: Sat, 8 Apr 2006
>>> 18:47:34 -0400 (EDT)
>>>
>>>> Hey,
>>>>
>>>> I have a kernel module that uses unregister_qdisc and
>>>> register_qdisc, whenever i try to insert the module I get:
>>>> /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o:
>>>> /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: unresolved symbol
>>>> unregister_qdisc /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o:
>>>> /lib/modules/2.4.32/kernel/net/sched/sch_xcp.o: unresolved symbol
>>>> register_qdisc
>>>>
>>>> Am i missing some sort of support in the kernel?
>>>
>>> Make sure CONFIG_NET_SCHED is enabled and that you compiled your
>>> module against that kernel.
>>>
>>> Where does this sch_xcp come from? It's not in the vanilla sources.
>>>
>>> Also, please direct networking questions to the
>>> netdev@vger.kernel.org mailing list which I have added to the CC:.
>
> --- ~Randy
>
>
--
next prev parent reply other threads:[~2006-04-09 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 22:47 George P Nychis
2006-04-08 22:54 ` David S. Miller
2006-04-08 23:18 ` George P Nychis
2006-04-08 23:37 ` Randy.Dunlap
2006-04-09 17:37 ` George P Nychis [this message]
2006-04-09 20:03 ` Randy.Dunlap
2006-04-09 20:06 ` George P Nychis
2006-04-10 2:05 ` George P Nychis
2006-04-10 2:29 ` Randy.Dunlap
2006-04-10 2:49 ` George P Nychis
2006-04-10 2:59 ` Randy.Dunlap
2006-04-10 3:20 ` George P Nychis
2006-04-10 3:29 ` Randy.Dunlap
2006-04-10 4:24 ` Willy Tarreau
2006-04-10 5:03 ` George P Nychis
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=1786.128.2.140.234.1144604245.squirrel@128.2.140.234 \
--to=gnychis@cmu.edu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.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
all inboxes | Powered by JetHome®