In case anyone else comes across this, there's a dependency for CRYPTO_CCM that wasn't enabled in my kernel. Somehow menuconfig didn't pick it up. Still have no idea why the compat_put_timespec line is failing to compile. I'm guessing it's another unmet dependency somewhere (I'm using a striped down ARM kernel)? On Tue, Apr 29, 2014 at 7:59 PM, Aaron Hamilton <aaron@xxxxxxxxxxxxxxxxxxxx> wrote: > In trying to compile backports-3.14-1 with a 2.6.39.4 kernel, I get > the following compilation errors: > > backport-include/linux/compat.h:18: error: expected ';', ',' or ')' > before '*' token > > If I comment out line 18 in compat.h which just reads "extern int > compat_put_timespec(const struct timespec*, void __user *)", then I > get past that error. > > Next, things get stuck on compat/crypto-ccm.c on lines 250 and 255, > stating "too few arguments to function 'scatterwalk_map'" and "too few > arguments to function 'scatterwalk_unmap'". Both of these function > calls pass only one argument, yet my kernel headers define the > functions with two parameters. > > I also checked for further references in compat code, but couldn't > find any declarations that map this function properly to one take a > single argument. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
