Re: CRC32=y && 8193TOO=m unresolved symbols

• Next message: Henning P. Schmiedehausen: "Re: Question about style when converting from K&R to ANSI C."
• Previous message: hugang: "software suspend in 2.5.70-mm3."
• In reply to: Stewart Smith: "CRC32=y && 8193TOO=m unresolved symbols"
• Next in thread: Stewart Smith: "[PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols"
• Reply: Stewart Smith: "[PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 2003-06-03 at 02:13, Stewart Smith wrote:
> this problem disappears when you have CONFIG_CRC32=y and
> CONFIG_8139TOO=y. It only happens when CRC32=y and 8139TOO=m
>
> Occurs on all 2.5.70 through bk6 (haven't tried later). Also on -mm3
>
> I get unresolved symbols for bitreverse and crc32_le.
>
> I've tried mucking around a bit with EXPORT_SYMBOL and the like, but I
> have to admit, i'm stumped. Help! :)

My current solution to this, which was sent to Alan but which didn't
appear in 2.4.21-rc6-ac2, is to export the symbols from kernel/ksyms.c
#ifdef CONFIG_CRC32 and from lib/crc32.c #ifndef CONFIG_CRC32.

That should work in all circumstances.

-- 
dwmw2
-
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/

• Next message: Henning P. Schmiedehausen: "Re: Question about style when converting from K&R to ANSI C."
• Previous message: hugang: "software suspend in 2.5.70-mm3."
• In reply to: Stewart Smith: "CRC32=y && 8193TOO=m unresolved symbols"
• Next in thread: Stewart Smith: "[PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols"
• Reply: Stewart Smith: "[PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:19 EST