From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Brian Litzinger <brian@top.worldcontrol.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: CIPE vs. GPLONLY_
Date: Sat, 12 Jan 2002 01:26:01 -0200 [thread overview]
Message-ID: <20020112032601.GA13389@conectiva.com.br> (raw)
In-Reply-To: <20020112010317.GA1765@top.worldcontrol.com> <E16PD12-0000wY-00@the-village.bc.nu> <20020112014830.GA6031@top.worldcontrol.com>
In-Reply-To: <20020112014830.GA6031@top.worldcontrol.com>
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
next prev parent reply other threads:[~2002-01-12 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-01-12 4:57 ` brian
2002-01-12 11:37 ` Olaf Titz
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=20020112032601.GA13389@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brian@top.worldcontrol.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox