From: Yonghong Song <yhs@fb.com>
To: Song Liu <song@kernel.org>, Quentin Monnet <quentin@isovalent.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next] bpftool: fix build failure
Date: Mon, 14 Sep 2020 09:55:44 -0700 [thread overview]
Message-ID: <c33a5edc-ea0a-e575-d229-d0aaf2812fa7@fb.com> (raw)
In-Reply-To: <CAPhsuW5Ja5if-DOPQn1FrbiEsH-YXXYVGzM59XQkyG5_xNmD-A@mail.gmail.com>
On 9/14/20 9:20 AM, Song Liu wrote:
> On Mon, Sep 14, 2020 at 1:20 AM Quentin Monnet <quentin@isovalent.com> wrote:
>>
>> On 14/09/2020 07:12, Yonghong Song wrote:
>>> When building bpf selftests like
>>> make -C tools/testing/selftests/bpf -j20
>>> I hit the following errors:
>>> ...
>>> GEN /net-next/tools/testing/selftests/bpf/tools/build/bpftool/Documentation/bpftool-gen.8
>>> <stdin>:75: (WARNING/2) Block quote ends without a blank line; unexpected unindent.
>>> <stdin>:71: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> <stdin>:85: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> <stdin>:57: (WARNING/2) Block quote ends without a blank line; unexpected unindent.
>>> <stdin>:66: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> <stdin>:109: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> <stdin>:175: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> <stdin>:273: (WARNING/2) Literal block ends without a blank line; unexpected unindent.
>>> make[1]: *** [/net-next/tools/testing/selftests/bpf/tools/build/bpftool/Documentation/bpftool-perf.8] Error 12
>>> make[1]: *** Waiting for unfinished jobs....
>>> make[1]: *** [/net-next/tools/testing/selftests/bpf/tools/build/bpftool/Documentation/bpftool-iter.8] Error 12
>>> make[1]: *** [/net-next/tools/testing/selftests/bpf/tools/build/bpftool/Documentation/bpftool-struct_ops.8] Error 12
>>> ...
>>>
>>> I am using:
>>> -bash-4.4$ rst2man --version
>>> rst2man (Docutils 0.11 [repository], Python 2.7.5, on linux2)
>>> -bash-4.4$
>>>
>>> Looks like that particular version of rst2man prefers to have a blank line
>>> after literal blocks. This patch added block lines in related .rst files
>>> and compilation can then pass.
>>>
>>> Cc: Quentin Monnet <quentin@isovalent.com>
>>> Fixes: 18841da98100 ("tools: bpftool: Automate generation for "SEE ALSO" sections in man pages")
>>> Signed-off-by: Yonghong Song <yhs@fb.com>
>>
>>
>> Hi Yonghong, thanks for the fix! I didn't see those warnings on my
>> setup. For the record my rst2man version is:
>>
>> rst2man (Docutils 0.16 [release], Python 3.8.2, on linux)
>>
>> Your patch looks good, but instead of having blank lines at the end of
>> most files, could you please check if the following works?
>>
>> ------
>>
>> diff --git a/tools/bpf/bpftool/Documentation/Makefile
>> b/tools/bpf/bpftool/Documentation/Makefile
>> index 4c9dd1e45244..01b30ed86eac 100644
>> --- a/tools/bpf/bpftool/Documentation/Makefile
>> +++ b/tools/bpf/bpftool/Documentation/Makefile
>> @@ -32,7 +32,7 @@ RST2MAN_OPTS += --verbose
>>
>> list_pages = $(sort $(basename $(filter-out $(1),$(MAN8_RST))))
>> see_also = $(subst " ",, \
>> - "\n" \
>> + "\n\n" \
>> "SEE ALSO\n" \
>> "========\n" \
>> "\t**bpf**\ (2),\n" \
>
> Yes, this works (I am using the same rst2man as Yonghong's).
Song, could you help check whether the following change works for you or
not?
@@ -44,7 +44,7 @@ $(OUTPUT)%.8: %.rst
ifndef RST2MAN_DEP
$(error "rst2man not found, but required to generate man pages")
endif
- $(QUIET_GEN)( cat $< ; echo -n $(call see_also,$<) ) | rst2man
$(RST2MAN_OPTS) > $@
+ $(QUIET_GEN)( cat $< ; echo -e $(call see_also,$<) ) | rst2man
$(RST2MAN_OPTS) > $@
clean: helpers-clean
$(call QUIET_CLEAN, Documentation)
>
> Thanks,
> Song
>
next prev parent reply other threads:[~2020-09-14 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 6:12 [PATCH bpf-next] bpftool: fix build failure Yonghong Song
2020-09-14 8:16 ` Quentin Monnet
2020-09-14 16:20 ` Song Liu
2020-09-14 16:55 ` Yonghong Song [this message]
2020-09-14 16:46 ` Yonghong Song
2020-09-14 16:54 ` Yonghong Song
2020-09-14 17:23 ` Quentin Monnet
2020-09-14 17:43 ` Yonghong Song
2020-09-14 17:55 ` Andrii Nakryiko
2020-09-14 18:06 ` Yonghong Song
2020-09-14 18:13 ` Andrii Nakryiko
2020-09-14 18:20 ` Yonghong Song
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=c33a5edc-ea0a-e575-d229-d0aaf2812fa7@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=song@kernel.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;
as well as URLs for NNTP newsgroup(s).