All of lore.kernel.org
 help / color / mirror / Atom feed
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 [rescued]
Date: Fri, 10 Jan 2003 19:38:52 +0100	[thread overview]
Message-ID: <200301101838.h0AIcqc05949@mail.intergenia.de> (raw)

--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Dave: (hope i'm addressing this issue to the right person!)

When making bzImage with the current BK I receive the following during=20
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...=20
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 =20
compile all 2.5.54 BK cleanly. What's the deal now?

Regards
Josh

--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+HovZ6TRUxq22Mx4RAgy7AJ9562vM9zS09EFq5b3r6xM/DHZ1bgCgvf0N
0awrVgvTCn1st7U20vlKm1c=
=XugU
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


                 reply	other threads:[~2003-01-10 18:40 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=200301101838.h0AIcqc05949@mail.intergenia.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.