From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Michael Ellerman <mpe@ellerman.id.au>,
David Ahern <dsahern@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: make -C tools clean failure on older systems
Date: Thu, 14 May 2015 19:42:22 +0200 [thread overview]
Message-ID: <20150514174222.GC19338@gmail.com> (raw)
In-Reply-To: <20150514155453.GI23588@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > > @@ -27,7 +27,7 @@ TARGETS_HOTPLUG += memory-hotplug
> > > # Makefile to avoid test build failures when test
> > > # Makefile doesn't have explicit build rules.
> > > ifeq (1,$(MAKELEVEL))
> > > -undefine LDFLAGS
> > > +override LDFLAGS =
> > > override MAKEFLAGS =
> > > endif
> >
> > I recall testing with override and remember it to not work. If you would
>
> bummer, then its not that easy, I thought it was an oversight, but
> if you tested it and it didn't work, nevermind, no need, I guess, to
> support older systems if it requires more, non trivial, work.
So what's the 'make' version cutoff for this capability?
We should not require insane hacks, the minimum required make version
for the kernel, as per Documentation/Changes, is v3.80:
o GNU make 3.80 # make --version
Thanks,
Ingo
next prev parent reply other threads:[~2015-05-14 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 15:12 make -C tools clean failure on older systems Arnaldo Carvalho de Melo
2015-05-14 15:39 ` Shuah Khan
2015-05-14 15:54 ` Arnaldo Carvalho de Melo
2015-05-14 17:42 ` Ingo Molnar [this message]
2015-05-14 20:00 ` Arnaldo Carvalho de Melo
2015-05-14 18:29 ` Shuah Khan
2015-05-14 19:48 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150514174222.GC19338@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=shuahkh@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.