From: Eric Dumazet <eric.dumazet@gmail.com>
To: Frank Peters <frank.peters@comcast.net>
Cc: linux-kernel@vger.kernel.org,
Bruce Allan <bruce.w.allan@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.38 Compile Failure e1000e Module
Date: Wed, 16 Mar 2011 16:16:57 +0100 [thread overview]
Message-ID: <1300288617.3202.10.camel@edumazet-laptop> (raw)
In-Reply-To: <20110316103318.19bd03e4.frank.peters@comcast.net>
Le mercredi 16 mars 2011 à 10:33 -0400, Frank Peters a écrit :
> Hello,
>
> I cannot compile kernel 2.6.38. Apparently, there is a build failure
> with the e1000e module (ethernet driver). The brief error message is this:
>
> ERROR: "crc32_le" [drivers/net/e1000e/e1000e.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> My compiler is gcc-4.5.2 on a Gentoo x64 system. The kernel source
> is the stock source from kernel.org.
>
> Please CC to frank.peters (at) comcast.net.
Hi Franck
Probably coming from commit fe46f58fa61f02
(e1000e: use either_crc_le() rather than re-write it)
Could you try following patch ?
Thanks
[PATCH] e1000e: fix kconfig for crc32 dependency
ERROR: "crc32_le" [drivers/net/e1000e/e1000e.ko] undefined!
Reported-by: Frank Peters <frank.peters@comcast.net>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Bruce Allan <bruce.w.allan@intel.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 0382332..90d1d3c 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -2098,6 +2098,7 @@ config E1000
config E1000E
tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
+ select CRC32
depends on PCI && (!SPARC32 || BROKEN)
---help---
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
next parent reply other threads:[~2011-03-16 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110316103318.19bd03e4.frank.peters@comcast.net>
2011-03-16 15:16 ` Eric Dumazet [this message]
2011-03-16 18:15 ` 2.6.38 Compile Failure e1000e Module David Miller
2011-03-16 15:21 ` [PATCH] net: " Randy Dunlap
2011-03-16 18:15 ` David Miller
2011-03-16 18:31 ` Randy Dunlap
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=1300288617.3202.10.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=frank.peters@comcast.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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