I finally ended up working around the problem by adding a copy statement in the kernel.spec file, just after it runs the scripts to generate the configs, to manually copy my working config file to the BUILD/kernel-*/linux-*/ folder. From there it looks like the scripts pick it up and then place it in to the BUILD/kernel-*/linux-*/configs/ folder. But initially I still am not sure where it tries to get them from initially. On 2018-02-07 09:46 AM, Chris Szilagyi wrote: > Hello: > I am following the CentOS instructions to compile a custom kernel for > ARM. I am following the instructions here: > https://wiki.centos.org/HowTos/Custom_Kernel. I do need my own config > which I have generated and copied to the directories as mentioned in > the instructions. > > I eventually get to the step and start the build with : rpmbuild -bb > --target=`uname -m` kernel.spec 2> build-err.log | tee build-out.log > > During the build, just after the "make -s mrproper", it tries to "cp > configs/kernel-4.9.75-armv7l.config", and gives the error "No such > file or directory". It seems that the BUILD/kernel-*/linux-*configs/ > directory is somehow being generated by some scripts, and the config I > need is not there. I can't seem to find out where it gets the config > files that it places in the configs folder. Can anybody shed some > light on this? > > I noticed that the running kernel is "armv7hl", and doing a "uname -m" > returns "armv7l" (missing the "h"). Not sure if this has anything to > do with it. > > Thank you! > > Chris > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev