[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=UEuWww=H=TY=E8JvEmrobDNi5+rbTXvTAmZ2brpK+sdg@mail.gmail.com>
Date: Mon, 12 Mar 2018 23:23:50 -0700
From: Doug Anderson <dianders@...omium.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Mathieu Malaterre <malat@...ian.org>,
Dave Hansen <dave.hansen@...el.com>,
Yang Shi <yang.s@...baba-inc.com>,
Guenter Roeck <linux@...ck-us.net>,
Matthias Kaehlcke <mka@...omium.org>,
Cao jin <caoj.fnst@...fujitsu.com>,
Arnd Bergmann <arnd@...db.de>,
Mark Charlebois <charlebm@...il.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v3 2/2] kbuild: Don't mess with the .cache.mk when root
Hi,
On Mon, Mar 12, 2018 at 11:16 PM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Douglas Anderson <dianders@...omium.org> wrote:
>
>> +# Don't create Makefile caches if running as root since they can't be deleted
>> +# easily; in the real world we might be root when doing "sudo make install"
>> +ifeq ($(shell id -u),0)
>> +export KBUILD_NOCACHE := 1
>> +endif
>
> Please don't do this - many prominent kernel developers build their kernels as
> root - this makes the build slower for them, and also bifurcates testing.
Ah, interesting. I hadn't realized that!
I'm OK with dropping this patch myself. It was mostly addressing a
potential problem pointed out by Masahiro Yamada when we were talking
about .cache.mk, but I don't think anyone has actually experienced the
problems listed in the CL description. I suppose the other option
would be to go back to keying off the "install" target (like v2 of
this patch did), but it kinda feels like if someone did "sudo make
install" and then followed up by a non-sudo "make" they probably would
be able to figure out how to fix it without much trouble (just do a
"sudo make clean").
In case it's not obvious, though, we should still try to land patch #1
of this series. That's a real problems that people reported when the
.cache.mk stuff first landed and then folks tried to upgrade their
gcc.
-Doug
Powered by blists - more mailing lists