On 24 July 2014 18:12, Sam Ravnborg <s...@ravnborg.org> wrote: > On Thu, Jul 24, 2014 at 04:24:48PM +0200, Ard Biesheuvel wrote: >> On 24 July 2014 16:18, Ard Biesheuvel <ard.biesheu...@linaro.org> wrote: >> > On 24 July 2014 15:40, Andreas Schwab <sch...@suse.de> wrote: >> >> Ard Biesheuvel <ard.biesheu...@linaro.org> writes: >> >> >> >>> On 24 July 2014 15:26, Andreas Schwab <sch...@suse.de> wrote: >> >>>> You are not using CONFIG_MODVERSIONS. >> >>>> >> >>> >> >>> I am >> >> >> >> No, you aren't, since you say that your .cmd contains a command to >> >> create aes-glue-ce.o, which with CONFIG_MODVERSIONS it doesn't. >> >> >> > >> > OK, you're right, it contains a command to create .tmp_aes-glue-ce.o. >> > But I am still not seeing the error you are seeing, strangely enough. >> >> OK, now I am seeing it. >> >> Acked-by: Ard Biesheuvel <ard.biesheu...@linaro.org> > > Jumping in the end of the thread here - sorry for that. >
No worries > Another way to solve this would be to create two > small wrapper files: > aes-glue-neon.c - which include aes-glue.c > aes-glue-ce.c that include aes-glue.c > > Then you could use standard kbuild support for building your module. > And we will not potentially break it when we change cc_o_c in the near future. > I see how that would fix this issue, but frankly, if we need to add .c files that only #include other .c files to support building multiple objects from a single .c file, I think the flaw is in the build system, and I would rather fix the build system instead. Cheers, Ard. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/