public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* CIPE vs. GPLONLY_
@ 2002-01-12  1:03 brian
  2002-01-12  1:31 ` Alan Cox
  0 siblings, 1 reply; 6+ messages in thread
From: brian @ 2002-01-12  1:03 UTC (permalink / raw)
  To: linux-kernel

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.

-- 
Brian Litzinger <brian@worldcontrol.com>

    Copyright (c) 2002 By Brian Litzinger, All Rights Reserved

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: CIPE vs. GPLONLY_
  2002-01-12  1:03 CIPE vs. GPLONLY_ brian
@ 2002-01-12  1:31 ` Alan Cox
  2002-01-12  1:48   ` brian
                     ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Alan Cox @ 2002-01-12  1:31 UTC (permalink / raw)
  To: brian; +Cc: linux-kernel

> 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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: CIPE vs. GPLONLY_
  2002-01-12  1:31 ` Alan Cox
@ 2002-01-12  1:48   ` brian
  2002-01-12  3:26     ` Arnaldo Carvalho de Melo
  2002-01-12  4:57   ` brian
  2002-01-12 11:37   ` Olaf Titz
  2 siblings, 1 reply; 6+ messages in thread
From: brian @ 2002-01-12  1:48 UTC (permalink / raw)
  To: Alan Cox; +Cc: linux-kernel

On Sat, Jan 12, 2002 at 01:31:24AM +0000, Alan Cox wrote:
> > 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.

-- 
Brian Litzinger <brian@worldcontrol.com>

    Copyright (c) 2002 By Brian Litzinger, All Rights Reserved

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: CIPE vs. GPLONLY_
  2002-01-12  1:48   ` brian
@ 2002-01-12  3:26     ` Arnaldo Carvalho de Melo
  0 siblings, 0 replies; 6+ messages in thread
From: Arnaldo Carvalho de Melo @ 2002-01-12  3:26 UTC (permalink / raw)
  To: Brian Litzinger, Alan Cox, linux-kernel

Em Fri, Jan 11, 2002 at 05:48:30PM -0800, brian@worldcontrol.com escreveu:
> On Sat, Jan 12, 2002 at 01:31:24AM +0000, Alan Cox wrote:
> > > 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.

probably because they use an old modutils package...

- Arnaldo

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: CIPE vs. GPLONLY_
  2002-01-12  1:31 ` Alan Cox
  2002-01-12  1:48   ` brian
@ 2002-01-12  4:57   ` brian
  2002-01-12 11:37   ` Olaf Titz
  2 siblings, 0 replies; 6+ messages in thread
From: brian @ 2002-01-12  4:57 UTC (permalink / raw)
  To: Alan Cox; +Cc: linux-kernel

On Sat, Jan 12, 2002 at 01:31:24AM +0000, Alan Cox wrote:
> > 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.

-- 
Brian Litzinger <brian@worldcontrol.com>

    Copyright (c) 2002 By Brian Litzinger, All Rights Reserved

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: CIPE vs. GPLONLY_
  2002-01-12  1:31 ` Alan Cox
  2002-01-12  1:48   ` brian
  2002-01-12  4:57   ` brian
@ 2002-01-12 11:37   ` Olaf Titz
  2 siblings, 0 replies; 6+ messages in thread
From: Olaf Titz @ 2002-01-12 11:37 UTC (permalink / raw)
  To: linux-kernel

> Add
>
> 	MODULE_LICENSE("GPL");
>
> to the cipe code and all will be well

That's already fixed in the CIPE CVS tree.

Olaf


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-01-12 11:52 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-12  1:03 CIPE vs. GPLONLY_ brian
2002-01-12  1:31 ` Alan Cox
2002-01-12  1:48   ` brian
2002-01-12  3:26     ` Arnaldo Carvalho de Melo
2002-01-12  4:57   ` brian
2002-01-12 11:37   ` Olaf Titz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox