CIPE vs. GPLONLY_
top# insmod /lib/modules/2.4.17/misc/cipcb.o/lib/modules/2.4.17/misc/cipcb.o: unresolved symbol sk_run_filter /lib/modules/2.4.17/misc/cipcb.o: Note: modules without a GPL compatible license cannot use GPLONLY_ symbols
running CIPE 1.5.2 I get the error above. Should I be bother the CIPE people with this? Or is this some kernel thingy that needs to be dealt with?
I remember reading on l-k a few times some stuff about GPLONLY_ but I have no idea what to do now that I've run into whatever the problem is that is caused by this?
CIPE is a GPL'ed program.
Signature · 3 lines
Brian Litzinger <[email protected]> Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
Quoted 3 lines
running CIPE 1.5.2 I get the error above. Should I be bother the CIPE people with this? Or is this some kernel thingy that needs to be dealt with?
Add
MODULE_LICENSE("GPL");to the cipe code and all will be well
Quoted 9 lines · Alan Cox
Quoted 3 lines
running CIPE 1.5.2 I get the error above. Should I be bother the CIPE people with this? Or is this some kernel thingy that needs to be dealt with?
Add
MODULE_LICENSE("GPL");to the cipe code and all will be well
Thanks. I added that and now I'm just left with sk_run_filter undef'ed without the GPLONLY_ warning.
I've deleted my kernel sources and am starting everything over from scratch. I checked that 'CONFIG_FILTER' was defined and all seemed in order, but still got the error.
I read through the last few months of the CIPE archives and there is no mention of such a problem. Others mention running with 2.4.17, hence my start over.
Signature · 3 lines
Brian Litzinger <[email protected]> Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
Em Fri, Jan 11, 2002 at 05:48:30PM -0800, [email protected] escreveu:
Quoted 11 lines · Alan Cox
Quoted 6 lines
Quoted 3 lines
running CIPE 1.5.2 I get the error above. Should I be bother the CIPE people with this? Or is this some kernel thingy that needs to be dealt with?
Add
MODULE_LICENSE("GPL");to the cipe code and all will be well
Thanks. I added that and now I'm just left with
sk_run_filterundef'ed without theGPLONLY_warning.
Quoted 7 lines
I've deleted my kernel sources and am starting everything over from scratch. I checked that '
CONFIG_FILTER' was defined and all seemed in order, but still got the error.I read through the last few months of the CIPE archives and there is no mention of such a problem. Others mention running with 2.4.17, hence my start over.
probably because they use an old modutils package...
- Arnaldo
Quoted 9 lines · Alan Cox
Quoted 3 lines
running CIPE 1.5.2 I get the error above. Should I be bother the CIPE people with this? Or is this some kernel thingy that needs to be dealt with?
Add
MODULE_LICENSE("GPL");to the cipe code and all will be well
As I posted in another email. The above changed helped but I still had one undef'ed reference.
I removed my linux source tree, rebuilt everything, and now it works fine.
Signature · 3 lines
Brian Litzinger <[email protected]> Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
Quoted 5 lines
Add
MODULE_LICENSE("GPL");to the cipe code and all will be well
That's already fixed in the CIPE CVS tree.
Olaf