On Tue, Aug 15, 2017 at 6:54 PM, John Covici <cov...@ccs.covici.com> wrote:
> What is your umask? I had troubles like this when I had too > aggressive umask of I think 027 rather than 022. It is indeed 027, and I wondered whether that might have been what was behind the error, hence I tried chmod -R 777 the entire kernel tree. But maybe that mask is doing something nasty during the actual config step apart from the kernel tree. I'll try backing off the umask. Thanks! John
