On Thursday 08 June 2006 03:57, Herbert Xu wrote: > On Wed, Jun 07, 2006 at 09:37:23PM +0200, Joachim Fritschi wrote: > > > > diff -uprN linux-2.6.17-rc5/crypto/Makefile > > linux-2.6.17-rc5.twofish/crypto/Makefile > > --- linux-2.6.17-rc5/crypto/Makefile 2006-06-07 18:43:24.000000000 > > +0200 > > +++ linux-2.6.17-rc5.twofish/crypto/Makefile 2006-06-04 > > 13:59:27.949797218 +0200 > > @@ -32,3 +32,5 @@ obj-$(CONFIG_CRYPTO_MICHAEL_MIC) += mich > > obj-$(CONFIG_CRYPTO_CRC32C) += crc32c.o > > > > obj-$(CONFIG_CRYPTO_TEST) += tcrypt.o > > + > > +twofish-objs := twofish_c.o twofish_common.o > > What do we gain by renaming twofish.c to twofish_c.c?
Solve the naming conflict when compiling. Seemed to me like it is impossible to create a twofish.o out of twofish.o and twofish_common.o . And since having the original module name seemed more important to me i changed the name. I didn't find any other way in documentation of the kernel makefiles. I hope this isn't another newbie mistake. =) -Joachim - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
