[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f63abe64-6d4f-1374-5fd3-874a34c1c22f@molgen.mpg.de>
Date: Sun, 13 Feb 2022 10:45:11 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Zhouyi Zhou <zhouzhouyi@...il.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
rcu <rcu@...r.kernel.org>,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: Set environment variable `KVM` makes build fail
Dear Zhouyi,
Am 13.02.22 um 09:07 schrieb Zhouyi Zhou:, and
> Thank you for your trust in me.
Thank you for your help.
> I think the following patch has a good explanation of what happened ;-)
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/testing/selftests/rcutorture/bin/torture.sh?id=a7d89cfb8e1269cb6d22453adba56b8d0218589f
> "The torture-test scripting's long-standing use of KVM as the
> environment variable tracking the pathname of the rcutorture directory
> now conflicts with allmodconfig builds due to the
> virt/kvm/Makefile.kvm file's use of this as a makefile variable"
Indeed. In my script I had added the remote for the rcu git archive, but
forgot to actually fetch the objects and refs, and missed the error
message in the output.
Sorry for the noise, though the variable name should probably
namespaced, as at least for the name `KVM` the chance are higher (still
very small) that it’s set in the environment.
Kind regards,
Paul
Powered by blists - more mailing lists