From: Shawn <core@enodev.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Help porting MPPE PPP patch
Date: 01 Mar 2003 12:36:47 -0600 [thread overview]
Message-ID: <1046543807.4607.10.camel@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1324 bytes --]
Hi! I'm posting to humbly ask for help...
I was wondering if one of you kind souls might like to help me port the
attached patch over to the current 2.5?
So far all I know how to do is, in place of the current
drivers/net/Makefile and drivers/net/Config.in patches are the
following:
->drivers/net/Kconfig:
config PPP_MPPE
tristate "PPP MPPE compression (encryption)"
->drivers/net/Makefile:
obj-$(CONFIG_PPP_MPPE) = ppp_mppe_compress.o sha1.o arcfour.o
But I end up with the following when I try to build the module. Those
symbols are in sha1.c and arcfour.c.
*** Warning: Can't handle class_mask in drivers/ieee1394/ohci1394:FFFFFF
*** Warning: "ppp_unregister_compressor"
[drivers/net/ppp_mppe_compress.ko] undefined!
*** Warning: "ppp_register_compressor"
[drivers/net/ppp_mppe_compress.ko] undefined!
*** Warning: "arcfour_encrypt" [drivers/net/ppp_mppe_compress.ko]
undefined!
*** Warning: "arcfour_setkey" [drivers/net/ppp_mppe_compress.ko]
undefined!
*** Warning: "SHA1_Final" [drivers/net/ppp_mppe_compress.ko] undefined!
*** Warning: "SHA1_Update" [drivers/net/ppp_mppe_compress.ko] undefined!
*** Warning: "SHA1_Init" [drivers/net/ppp_mppe_compress.ko] undefined!
*** Warning: "page_states__per_cpu" [fs/nfs/nfs.ko] has no CRC!
Any help would be endlessly appreciated.
[-- Attachment #1.2: linux-2.4.18-19.8.0-poptop.patch.gz --]
[-- Type: application/x-gzip, Size: 10760 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-03-01 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 18:36 Shawn [this message]
2003-03-01 23:46 ` Shawn
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=1046543807.4607.10.camel@localhost.localdomain \
--to=core@enodev.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
all inboxes | Powered by JetHome®