2.5.60: .o or .ko for CONFIG_MODVERSIONS?

Adam J. Richter (adam@yggdrasil.com)
Tue, 11 Feb 2003 02:13:56 -0800

I just tried to build 2.5.60 with CONFIG_MODVERSIONS.
It tries to build modules with the .o extension instead of .ko,
but "make modules_install" still expects modules to be have a ,ko
extension.

Building with CONFIG_MODVERSIONS generates modules with a .ko
extension.

I assume this is a bug in the newly restored
CONFIG_MODVERSIONS option, although I'd be happy to have modules use
the .o extension again.

Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."

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