From: Yonghong Song <yhs@fb.com>
To: Ben Hutchings <benh@debian.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: <bpf@vger.kernel.org>, <debian-kernel@lists.debian.org>
Subject: Re: [PATCH] bpftool: Fix version string in recursive builds
Date: Fri, 14 Aug 2020 15:55:06 -0700 [thread overview]
Message-ID: <cda9dba0-230d-3cc6-7f53-6ee83ec6f81d@fb.com> (raw)
In-Reply-To: <ebf711740484b0a489f11b749d0f00d30be5a5b1.camel@debian.org>
On 8/14/20 3:17 PM, Ben Hutchings wrote:
> On Fri, 2020-08-14 at 08:43 -0700, Yonghong Song wrote:
> [...]
>> I tried the following
>>
>> --- a/tools/bpf/bpftool/Makefile
>> +++ b/tools/bpf/bpftool/Makefile
>> @@ -25,7 +25,7 @@ endif
>>
>> LIBBPF = $(LIBBPF_PATH)libbpf.a
>>
>> -BPFTOOL_VERSION := $(shell make -rR --no-print-directory -sC ../../..
>> kernelversion)
>> +BPFTOOL_VERSION := $(shell MAKEFLAGS=w make -rR --no-print-directory
>> -sC ../../.. kernelversion)
>>
>> -bash-4.4$ ./bpftool version
>> ./bpftool v5.8.0
>>
>> I set env variable MAKEFLAGS=w, and build bpftool it works fine too.
>> Maybe I miss something or debian changed top level Makefile?
>
> Yes, but we don't change MAKEFLAGS or any of the logic around quietness
> or verbosity.
>
> I assume there are other factors involved, as I've also been unable to
> construct a simple reproducer.
It would be good to know what is the exact problem, and then we can
decide whether this patch is the most appropriate fix or not.
>
> Ben.
>
>> I am testing against latest bpf tree.
>>
>>>
>>> $(LIBBPF): FORCE
>>> $(if $(LIBBPF_OUTPUT),@mkdir -p $(LIBBPF_OUTPUT))
>>>
prev parent reply other threads:[~2020-08-14 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 23:58 [PATCH] bpftool: Fix version string in recursive builds Ben Hutchings
2020-08-14 15:43 ` Yonghong Song
2020-08-14 22:17 ` Ben Hutchings
2020-08-14 22:55 ` Yonghong Song [this message]
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=cda9dba0-230d-3cc6-7f53-6ee83ec6f81d@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=benh@debian.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=debian-kernel@lists.debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox