From: "Michael Chan" <mchan@broadcom.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: linux-2.6.17(.6): bnx2.c:(.text+0xd741e): undefined reference to `crc32_le'
Date: Mon, 24 Jul 2006 13:00:33 -0700 [thread overview]
Message-ID: <1153771233.3167.8.camel@rh4> (raw)
In-Reply-To: <200607211406.39982.toralf.foerster@gmx.de>
On Fri, 2006-07-21 at 05:06 -0700, Toralf Förster wrote:
> Compiling (an exotic ?) config I got:
>
> ...
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `bnx2_set_rx_mode':
> bnx2.c:(.text+0xd741e): undefined reference to `crc32_le'
> drivers/built-in.o: In function `bnx2_test_nvram':
> bnx2.c:(.text+0xd9a5f): undefined reference to `crc32_le'
> bnx2.c:(.text+0xd9a83): undefined reference to `crc32_le'
> make: *** [.tmp_vmlinux1] Error 1
>
BNX2 requires the CRC32 library and the current kernels do not have that
dependency in the Kconfig. This has been fixed and will be in 2.6.18.
For now, you can turn on CONFIG_CRC32 (to y) and that should fix the
problem.
Thanks.
prev parent reply other threads:[~2006-07-24 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 12:06 linux-2.6.17(.6): bnx2.c:(.text+0xd741e): undefined reference to `crc32_le' Toralf Förster
2006-07-24 20:00 ` Michael Chan [this message]
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=1153771233.3167.8.camel@rh4 \
--to=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).