From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Norbert Preining <preining@logic.at>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] pcmcia: select crc32 in Kconfig for PCMCIA [Was: Re: pcmcia compile problems in 2.6.11-mm4 and above]
Date: Mon, 21 Mar 2005 20:13:53 +0100 [thread overview]
Message-ID: <20050321191353.GA13659@isilmar.linta.de> (raw)
In-Reply-To: <20050321150143.GB14614@gamma.logic.tuwien.ac.at>
On Mon, Mar 21, 2005 at 04:01:43PM +0100, Norbert Preining wrote:
> HI Andrew!
>
> Compiling 2.6.12-rc1-mm1 with the attached config gives me an error
> while compiling pcmcia (I made a make oldconfig)
> drivers/built-in.o(.text+0xaf2a2): In function `pcmcia_check_driver':
> : undefined reference to `crc32_le'
> drivers/built-in.o(.text+0xafef1): In function `pcmcia_bus_hotplug':
> : undefined reference to `crc32_le'
>
> compiling pcmcia modular works.
That's a missing dependency on CONFIG_CRC32. Could you check whether this
patch helps, please?
PCMCIA needs CRC32.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Index: linux-2.6.12-rc1/drivers/pcmcia/Kconfig
===================================================================
--- linux-2.6.12-rc1.orig/drivers/pcmcia/Kconfig 2005-03-21 20:07:42.000000000 +0100
+++ linux-2.6.12-rc1/drivers/pcmcia/Kconfig 2005-03-21 20:12:00.000000000 +0100
@@ -42,6 +42,7 @@
config PCMCIA
tristate "16-bit PCMCIA support"
+ select CRC32
default y
---help---
This option enables support for 16-bit PCMCIA cards. Most older
next prev parent reply other threads:[~2005-03-21 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 15:01 pcmcia compile problems in 2.6.11-mm4 and above Norbert Preining
2005-03-21 19:13 ` Dominik Brodowski [this message]
2005-03-21 20:00 ` [PATCH 1/1] pcmcia: select crc32 in Kconfig for PCMCIA [Was: Re: pcmcia compile problems in 2.6.11-mm4 and above] Norbert Preining
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=20050321191353.GA13659@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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®