From: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
To: davem@ninka.net
Cc: linux-kernel@vger.kernel.org
Subject: Some 2.5.55 compile problems
Date: Fri, 10 Jan 2003 01:01:13 -0800 [thread overview]
Message-ID: <20030110090113.GA5114@kamui> (raw)
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi Dave: (hope i'm addressing this issue to the right person!)
When making bzImage with the current BK I receive the following during
the final link process:
net/built-in.o(.text+0x4ba22): In function `xfrm_probe_algs':
: undefined reference to `crypto_alg_available'
net/built-in.o(.text+0x4ba68): In function `xfrm_probe_algs':
: undefined reference to `crypto_alg_available'
this is because ipv4 seems to depend on some Cryptographic API stuff...
that doesn't sound right though! Anyway, I added base Cryptographic API
support to shut it up, and the link went fine.
But this was definitely not added until recently - I was able to
compile all 2.5.54 BK cleanly. What's the deal now?
Regards
Josh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-01-10 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030110090113.GA5114@kamui \
--to=joshk@ludicrus.ath.cx \
--cc=davem@ninka.net \
--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