Re: 4.2-rc0: akcipher breaks compilation

From: Pavel Machek
Date: Wed Jul 01 2015 - 04:54:42 EST


On Tue 2015-06-30 22:48:26, Herbert Xu wrote:
> On Tue, Jun 30, 2015 at 11:27:50AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > CC crypto/akcipher.o
> > CC block/bio.o
> > crypto/akcipher.c: In function âcrypto_akcipher_reportâ:
> > crypto/akcipher.c:30:32: error: storage size of ârakcipherâ isnât
> > known
> > struct crypto_report_akcipher rakcipher;
> > ^
> > crypto/akcipher.c:34:19: error:
> > âCRYPTOCFGA_REPORT_AKCIPHERâ undeclared (first use in this
> > function)
> > if (nla_put(skb, CRYPTOCFGA_REPORT_AKCIPHER,
> > ^
> > crypto/akcipher.c:34:19: note: each
> > undeclared identifier is reported only once for each function it
> > appears in
> > crypto/akcipher.c:35:14: error: invalid application of âsizeofâ to
> > incomplete type âstruct crypto_report_akcipherâ
> > sizeof(struct crypto_report_akcipher), &rakcipher))
> > ^
> > crypto/akcipher.c:30:32: warning: unused
> > variable ârakcipherâ [-Wunused-variable]
> > struct crypto_report_akcipher rakcipher;
> > ^
> > scripts/Makefile.build:258:
> > recipe for target 'crypto/akcipher.o' failed
> > make[1]: *** [crypto/akcipher.o] Error 1
> > Makefile:945: recipe for target 'crypto' failed
> > make: *** [crypto] Error 2
> > make: *** Waiting for unfinished jobs....
>
> That's weird. both symbols are meant to be defined in
> include/uapi/linux/cryptouser.h. Do you have that file and is
> it up-to-date? Do you happen to have an obsolete
> include/linux/cryptouser.h file in your tree?

I had the file, but probably had other copy of cryptouser.h somewhere.

git --work-tree=/data/l/linux-64 clean -df

helped. Thanks and sorry for the noise,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/