All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH bpf-next] bpftool: fix build failure
@ 2020-09-14  6:12 Yonghong Song
  2020-09-14  8:16 ` Quentin Monnet
  0 siblings, 1 reply; 12+ messages in thread
From: Yonghong Song @ 2020-09-14  6:12 UTC (permalink / raw)
  To: bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team, Quentin Monnet

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>
---
 tools/bpf/bpftool/Documentation/bpftool-cgroup.rst     | 1 +
 tools/bpf/bpftool/Documentation/bpftool-feature.rst    | 1 +
 tools/bpf/bpftool/Documentation/bpftool-iter.rst       | 1 +
 tools/bpf/bpftool/Documentation/bpftool-link.rst       | 1 +
 tools/bpf/bpftool/Documentation/bpftool-map.rst        | 1 +
 tools/bpf/bpftool/Documentation/bpftool-net.rst        | 1 +
 tools/bpf/bpftool/Documentation/bpftool-perf.rst       | 1 +
 tools/bpf/bpftool/Documentation/bpftool-prog.rst       | 1 +
 tools/bpf/bpftool/Documentation/bpftool-struct_ops.rst | 1 +
 tools/bpf/bpftool/Documentation/bpftool.rst            | 1 +
 10 files changed, 10 insertions(+)

diff --git a/tools/bpf/bpftool/Documentation/bpftool-cgroup.rst b/tools/bpf/bpftool/Documentation/bpftool-cgroup.rst
index 790944c35602..5d01a74b7c57 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-cgroup.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-cgroup.rst
@@ -143,3 +143,4 @@ EXAMPLES
 ::
 
     ID       AttachType      AttachFlags     Name
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-feature.rst b/tools/bpf/bpftool/Documentation/bpftool-feature.rst
index dd3771bdbc57..e6b4b9efc6f7 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-feature.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-feature.rst
@@ -72,3 +72,4 @@ DESCRIPTION
 OPTIONS
 =======
 	.. include:: common_options.rst
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-iter.rst b/tools/bpf/bpftool/Documentation/bpftool-iter.rst
index 51f49bead619..30bfe3b1f529 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-iter.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-iter.rst
@@ -68,3 +68,4 @@ EXAMPLES
 
    Create a file-based bpf iterator from bpf_iter_hashmap.o and map with
    id 20, and pin it to /sys/fs/bpf/my_hashmap
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-link.rst b/tools/bpf/bpftool/Documentation/bpftool-link.rst
index 5f7db2a837cc..6d1ff68c5d6f 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-link.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-link.rst
@@ -106,3 +106,4 @@ EXAMPLES
 ::
 
     -rw------- 1 root root 0 Apr 23 21:39 link
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-map.rst b/tools/bpf/bpftool/Documentation/bpftool-map.rst
index dade10cdf295..6500612f4723 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-map.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-map.rst
@@ -270,3 +270,4 @@ would be lost as soon as bpftool exits).
 
   key: 00 00 00 00  value: 22 02 00 00
   Found 1 element
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-net.rst b/tools/bpf/bpftool/Documentation/bpftool-net.rst
index d8165d530937..8450f7b9a10d 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-net.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-net.rst
@@ -172,3 +172,4 @@ EXAMPLES
 ::
 
       xdp:
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-perf.rst b/tools/bpf/bpftool/Documentation/bpftool-perf.rst
index e958ce91de72..1b5202d3d9ac 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-perf.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-perf.rst
@@ -63,3 +63,4 @@ EXAMPLES
      {"pid":21765,"fd":5,"prog_id":7,"fd_type":"kretprobe","func":"__x64_sys_nanosleep","offset":0}, \
      {"pid":21767,"fd":5,"prog_id":8,"fd_type":"tracepoint","tracepoint":"sys_enter_nanosleep"}, \
      {"pid":21800,"fd":5,"prog_id":9,"fd_type":"uprobe","filename":"/home/yhs/a.out","offset":1159}]
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-prog.rst b/tools/bpf/bpftool/Documentation/bpftool-prog.rst
index 358c7309d419..3c7a90915d45 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-prog.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-prog.rst
@@ -326,3 +326,4 @@ EXAMPLES
       40176203 cycles                                                 (83.05%)
       42518139 instructions    #   1.06 insns per cycle               (83.39%)
            123 llc_misses      #   2.89 LLC misses per million insns  (83.15%)
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool-struct_ops.rst b/tools/bpf/bpftool/Documentation/bpftool-struct_ops.rst
index 506e70ee78e9..ccfd215b17a0 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-struct_ops.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-struct_ops.rst
@@ -82,3 +82,4 @@ EXAMPLES
 ::
 
    Registered tcp_congestion_ops cubic id 110
+
diff --git a/tools/bpf/bpftool/Documentation/bpftool.rst b/tools/bpf/bpftool/Documentation/bpftool.rst
index e7d949334961..1026f15b5c64 100644
--- a/tools/bpf/bpftool/Documentation/bpftool.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool.rst
@@ -54,3 +54,4 @@ OPTIONS
 	-n, --nomount
 		  Do not automatically attempt to mount any virtual file system
 		  (such as tracefs or BPF virtual file system) when necessary.
+
-- 
2.24.1


^ permalink raw reply related	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  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:46   ` Yonghong Song
  0 siblings, 2 replies; 12+ messages in thread
From: Quentin Monnet @ 2020-09-14  8:16 UTC (permalink / raw)
  To: Yonghong Song, bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team

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" \

^ permalink raw reply related	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14  8:16 ` Quentin Monnet
@ 2020-09-14 16:20   ` Song Liu
  2020-09-14 16:55     ` Yonghong Song
  2020-09-14 16:46   ` Yonghong Song
  1 sibling, 1 reply; 12+ messages in thread
From: Song Liu @ 2020-09-14 16:20 UTC (permalink / raw)
  To: Quentin Monnet
  Cc: Yonghong Song, bpf, Networking, Alexei Starovoitov,
	Daniel Borkmann, Kernel Team

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).

Thanks,
Song

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14  8:16 ` Quentin Monnet
  2020-09-14 16:20   ` Song Liu
@ 2020-09-14 16:46   ` Yonghong Song
  2020-09-14 16:54     ` Yonghong Song
  1 sibling, 1 reply; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 16:46 UTC (permalink / raw)
  To: Quentin Monnet, bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team



On 9/14/20 1:16 AM, Quentin Monnet 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?

Thanks for the tip! I looked at the generated output again. My above fix 
can silent the warning, but certainly not correct.

With the following change, I captured the intermediate result of the 
.rst file.

  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 -n $(call see_also,$<) ) | tee 
/tmp/tt | rst2man $(RST2MAN_OPTS) > $@

With below command,
    make clean && make bpftool-cgroup.8
I can get the new .rst file for bpftool-cgroup.

At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see

     ID       AttachType      AttachFlags     Name
\n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\ 
(7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\ 
(8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\ 
(8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\ 
(8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\ 
(8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\ 
(8),\n\t**bpftool-struct_ops**\ (8)\n

This sounds correct if we rst2man can successfully transforms '\n'
or '\t' to proper encoding in the man page.

Unfortunately, with my version of rst2man, I got

.IP "System Message: WARNING/2 (<stdin>:, line 146)"
Literal block ends without a blank line; unexpected unindent.
.sp
n SEE 
ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
.\" Generated by docutils manpage writer.

The rst2man simply considered \n as 'n'. The same for '\t' and
this caused the issue.

I did not find a way to fix the problem yet.

> 
> ------
> 
> 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" \
> 

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 16:46   ` Yonghong Song
@ 2020-09-14 16:54     ` Yonghong Song
  2020-09-14 17:23       ` Quentin Monnet
  0 siblings, 1 reply; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 16:54 UTC (permalink / raw)
  To: Quentin Monnet, bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team



On 9/14/20 9:46 AM, Yonghong Song wrote:
> 
> 
> On 9/14/20 1:16 AM, Quentin Monnet 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?
> 
> Thanks for the tip! I looked at the generated output again. My above fix 
> can silent the warning, but certainly not correct.
> 
> With the following change, I captured the intermediate result of the 
> .rst file.
> 
>   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 -n $(call see_also,$<) ) | tee 
> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
> 
> With below command,
>     make clean && make bpftool-cgroup.8
> I can get the new .rst file for bpftool-cgroup.
> 
> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
> 
>      ID       AttachType      AttachFlags     Name
> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\ 
> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\ 
> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\ 
> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\ 
> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\ 
> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\ 
> (8),\n\t**bpftool-struct_ops**\ (8)\n
> 
> This sounds correct if we rst2man can successfully transforms '\n'
> or '\t' to proper encoding in the man page.
> 
> Unfortunately, with my version of rst2man, I got
> 
> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
> Literal block ends without a blank line; unexpected unindent.
> .sp
> n SEE 
> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n 
> 
> .\" Generated by docutils manpage writer.
> 
> The rst2man simply considered \n as 'n'. The same for '\t' and
> this caused the issue.
> 
> I did not find a way to fix the problem yet.

The following change works for me.

@@ -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)
-bash-4.4$

I will send revision 2 shortly.

> 
>>
>> ------
>>
>> 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" \
>>

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 16:20   ` Song Liu
@ 2020-09-14 16:55     ` Yonghong Song
  0 siblings, 0 replies; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 16:55 UTC (permalink / raw)
  To: Song Liu, Quentin Monnet
  Cc: bpf, Networking, Alexei Starovoitov, Daniel Borkmann, Kernel Team



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
> 

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 16:54     ` Yonghong Song
@ 2020-09-14 17:23       ` Quentin Monnet
  2020-09-14 17:43         ` Yonghong Song
  0 siblings, 1 reply; 12+ messages in thread
From: Quentin Monnet @ 2020-09-14 17:23 UTC (permalink / raw)
  To: Yonghong Song, bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team, Andrii Nakryiko

On 14/09/2020 17:54, Yonghong Song wrote:
> 
> 
> On 9/14/20 9:46 AM, Yonghong Song wrote:
>>
>>
>> On 9/14/20 1:16 AM, Quentin Monnet 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?
>>
>> Thanks for the tip! I looked at the generated output again. My above
>> fix can silent the warning, but certainly not correct.
>>
>> With the following change, I captured the intermediate result of the
>> .rst file.
>>
>>   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 -n $(call see_also,$<) ) | tee
>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
>>
>> With below command,
>>     make clean && make bpftool-cgroup.8
>> I can get the new .rst file for bpftool-cgroup.
>>
>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
>>
>>      ID       AttachType      AttachFlags     Name
>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
>> (8),\n\t**bpftool-struct_ops**\ (8)\n
>>
>> This sounds correct if we rst2man can successfully transforms '\n'
>> or '\t' to proper encoding in the man page.
>>
>> Unfortunately, with my version of rst2man, I got
>>
>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
>> Literal block ends without a blank line; unexpected unindent.
>> .sp
>> n SEE
>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
>>
>> .\" Generated by docutils manpage writer.
>>
>> The rst2man simply considered \n as 'n'. The same for '\t' and
>> this caused the issue.
>>
>> I did not find a way to fix the problem https://www.google.com/url?q=https://zoom.us/j/94864957378?pwd%3DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09&sa=D&source=calendar&ust=1600532408208000&usg=AOvVaw3SJ0i8oz4ZM-GRb7hYkrYlyet.
> 
> The following change works for me.
> 
> @@ -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)
> -bash-4.4$
> 
> I will send revision 2 shortly.

Thanks Yonghong, but this does not work on my setup :/. The version of
echo which is called on my machine from the Makefile does not seem to
interpret the "-e" option and writes something like "-e\nSEE ALSO",
which causes rst2man to complain.

I suspect the portable option here would be printf, even though Andrii
had some concerns that we could pass a format specifier through the file
names [0].

Would this work on your setup?

	$(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...

Would that be acceptable?

[0]
https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e

Quentin

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 17:23       ` Quentin Monnet
@ 2020-09-14 17:43         ` Yonghong Song
  2020-09-14 17:55           ` Andrii Nakryiko
  0 siblings, 1 reply; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 17:43 UTC (permalink / raw)
  To: Quentin Monnet, bpf, netdev
  Cc: Alexei Starovoitov, Daniel Borkmann, kernel-team, Andrii Nakryiko



On 9/14/20 10:23 AM, Quentin Monnet wrote:
> On 14/09/2020 17:54, Yonghong Song wrote:
>>
>>
>> On 9/14/20 9:46 AM, Yonghong Song wrote:
>>>
>>>
>>> On 9/14/20 1:16 AM, Quentin Monnet 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?
>>>
>>> Thanks for the tip! I looked at the generated output again. My above
>>> fix can silent the warning, but certainly not correct.
>>>
>>> With the following change, I captured the intermediate result of the
>>> .rst file.
>>>
>>>    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 -n $(call see_also,$<) ) | tee
>>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
>>>
>>> With below command,
>>>      make clean && make bpftool-cgroup.8
>>> I can get the new .rst file for bpftool-cgroup.
>>>
>>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
>>>
>>>       ID       AttachType      AttachFlags     Name
>>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
>>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
>>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
>>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
>>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
>>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
>>> (8),\n\t**bpftool-struct_ops**\ (8)\n
>>>
>>> This sounds correct if we rst2man can successfully transforms '\n'
>>> or '\t' to proper encoding in the man page.
>>>
>>> Unfortunately, with my version of rst2man, I got
>>>
>>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
>>> Literal block ends without a blank line; unexpected unindent.
>>> .sp
>>> n SEE
>>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
>>>
>>> .\" Generated by docutils manpage writer.
>>>
>>> The rst2man simply considered \n as 'n'. The same for '\t' and
>>> this caused the issue.
>>>
>>> I did not find a way to fix the problem https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-3A__zoom.us_j_94864957378-3Fpwd-253DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09-26sa-3DD-26source-3Dcalendar-26ust-3D1600532408208000-26usg-3DAOvVaw3SJ0i8oz4ZM-2DGRb7hYkrYlyet&d=DwIDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=kEK7ScPMF-y-i8dli-or8wWEGREW5V4qPB7UqHqDnkg&s=Br0g0MFXxL_pJuDVTOY5UrmvfD2ru_6Uf_X_8Nr2Rhk&e= .
>>
>> The following change works for me.
>>
>> @@ -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)
>> -bash-4.4$
>>
>> I will send revision 2 shortly.
> 
> Thanks Yonghong, but this does not work on my setup :/. The version of
> echo which is called on my machine from the Makefile does not seem to
> interpret the "-e" option and writes something like "-e\nSEE ALSO",
> which causes rst2man to complain.
> 
> I suspect the portable option here would be printf, even though Andrii
> had some concerns that we could pass a format specifier through the file
> names [0].
> 
> Would this work on your setup?
> 
> 	$(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...
> 
> Would that be acceptable?

It works for me. Andrii originally suggested `echo -e`, but since `echo 
-e` does not work in your environment let us use printf then. I will add
a comment about '%' in the bpftool man page name.

> 
> [0]
> https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e
> 
> Quentin
> 

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 17:43         ` Yonghong Song
@ 2020-09-14 17:55           ` Andrii Nakryiko
  2020-09-14 18:06             ` Yonghong Song
  0 siblings, 1 reply; 12+ messages in thread
From: Andrii Nakryiko @ 2020-09-14 17:55 UTC (permalink / raw)
  To: Yonghong Song
  Cc: Quentin Monnet, bpf, Networking, Alexei Starovoitov,
	Daniel Borkmann, Kernel Team, Andrii Nakryiko

On Mon, Sep 14, 2020 at 10:46 AM Yonghong Song <yhs@fb.com> wrote:
>
>
>
> On 9/14/20 10:23 AM, Quentin Monnet wrote:
> > On 14/09/2020 17:54, Yonghong Song wrote:
> >>
> >>
> >> On 9/14/20 9:46 AM, Yonghong Song wrote:
> >>>
> >>>
> >>> On 9/14/20 1:16 AM, Quentin Monnet 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?
> >>>
> >>> Thanks for the tip! I looked at the generated output again. My above
> >>> fix can silent the warning, but certainly not correct.
> >>>
> >>> With the following change, I captured the intermediate result of the
> >>> .rst file.
> >>>
> >>>    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 -n $(call see_also,$<) ) | tee
> >>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
> >>>
> >>> With below command,
> >>>      make clean && make bpftool-cgroup.8
> >>> I can get the new .rst file for bpftool-cgroup.
> >>>
> >>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
> >>>
> >>>       ID       AttachType      AttachFlags     Name
> >>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
> >>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
> >>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
> >>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
> >>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
> >>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
> >>> (8),\n\t**bpftool-struct_ops**\ (8)\n
> >>>
> >>> This sounds correct if we rst2man can successfully transforms '\n'
> >>> or '\t' to proper encoding in the man page.
> >>>
> >>> Unfortunately, with my version of rst2man, I got
> >>>
> >>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
> >>> Literal block ends without a blank line; unexpected unindent.
> >>> .sp
> >>> n SEE
> >>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
> >>>
> >>> .\" Generated by docutils manpage writer.
> >>>
> >>> The rst2man simply considered \n as 'n'. The same for '\t' and
> >>> this caused the issue.
> >>>
> >>> I did not find a way to fix the problem https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-3A__zoom.us_j_94864957378-3Fpwd-253DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09-26sa-3DD-26source-3Dcalendar-26ust-3D1600532408208000-26usg-3DAOvVaw3SJ0i8oz4ZM-2DGRb7hYkrYlyet&d=DwIDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=kEK7ScPMF-y-i8dli-or8wWEGREW5V4qPB7UqHqDnkg&s=Br0g0MFXxL_pJuDVTOY5UrmvfD2ru_6Uf_X_8Nr2Rhk&e= .
> >>
> >> The following change works for me.
> >>
> >> @@ -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)
> >> -bash-4.4$
> >>
> >> I will send revision 2 shortly.
> >
> > Thanks Yonghong, but this does not work on my setup :/. The version of
> > echo which is called on my machine from the Makefile does not seem to
> > interpret the "-e" option and writes something like "-e\nSEE ALSO",
> > which causes rst2man to complain.
> >
> > I suspect the portable option here would be printf, even though Andrii
> > had some concerns that we could pass a format specifier through the file
> > names [0].
> >
> > Would this work on your setup?
> >
> >       $(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...
> >
> > Would that be acceptable?
>
> It works for me. Andrii originally suggested `echo -e`, but since `echo
> -e` does not work in your environment let us use printf then. I will add
> a comment about '%' in the bpftool man page name.

It's amazing how incompatible echo can be. But that aside, I have
nothing against printf itself, but:

printf "%s" "whatever we want to print out"

seems like the way to go, similarly how you'd do it in your C code, no?

>
> >
> > [0]
> > https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e
> >
> > Quentin
> >

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 17:55           ` Andrii Nakryiko
@ 2020-09-14 18:06             ` Yonghong Song
  2020-09-14 18:13               ` Andrii Nakryiko
  0 siblings, 1 reply; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 18:06 UTC (permalink / raw)
  To: Andrii Nakryiko
  Cc: Quentin Monnet, bpf, Networking, Alexei Starovoitov,
	Daniel Borkmann, Kernel Team, Andrii Nakryiko



On 9/14/20 10:55 AM, Andrii Nakryiko wrote:
> On Mon, Sep 14, 2020 at 10:46 AM Yonghong Song <yhs@fb.com> wrote:
>>
>>
>>
>> On 9/14/20 10:23 AM, Quentin Monnet wrote:
>>> On 14/09/2020 17:54, Yonghong Song wrote:
>>>>
>>>>
>>>> On 9/14/20 9:46 AM, Yonghong Song wrote:
>>>>>
>>>>>
>>>>> On 9/14/20 1:16 AM, Quentin Monnet 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?
>>>>>
>>>>> Thanks for the tip! I looked at the generated output again. My above
>>>>> fix can silent the warning, but certainly not correct.
>>>>>
>>>>> With the following change, I captured the intermediate result of the
>>>>> .rst file.
>>>>>
>>>>>     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 -n $(call see_also,$<) ) | tee
>>>>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
>>>>>
>>>>> With below command,
>>>>>       make clean && make bpftool-cgroup.8
>>>>> I can get the new .rst file for bpftool-cgroup.
>>>>>
>>>>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
>>>>>
>>>>>        ID       AttachType      AttachFlags     Name
>>>>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
>>>>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
>>>>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
>>>>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
>>>>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
>>>>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
>>>>> (8),\n\t**bpftool-struct_ops**\ (8)\n
>>>>>
>>>>> This sounds correct if we rst2man can successfully transforms '\n'
>>>>> or '\t' to proper encoding in the man page.
>>>>>
>>>>> Unfortunately, with my version of rst2man, I got
>>>>>
>>>>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
>>>>> Literal block ends without a blank line; unexpected unindent.
>>>>> .sp
>>>>> n SEE
>>>>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
>>>>>
>>>>> .\" Generated by docutils manpage writer.
>>>>>
>>>>> The rst2man simply considered \n as 'n'. The same for '\t' and
>>>>> this caused the issue.
>>>>>
>>>>> I did not find a way to fix the problem https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-3A__zoom.us_j_94864957378-3Fpwd-253DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09-26sa-3DD-26source-3Dcalendar-26ust-3D1600532408208000-26usg-3DAOvVaw3SJ0i8oz4ZM-2DGRb7hYkrYlyet&d=DwIDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=kEK7ScPMF-y-i8dli-or8wWEGREW5V4qPB7UqHqDnkg&s=Br0g0MFXxL_pJuDVTOY5UrmvfD2ru_6Uf_X_8Nr2Rhk&e= .
>>>>
>>>> The following change works for me.
>>>>
>>>> @@ -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)
>>>> -bash-4.4$
>>>>
>>>> I will send revision 2 shortly.
>>>
>>> Thanks Yonghong, but this does not work on my setup :/. The version of
>>> echo which is called on my machine from the Makefile does not seem to
>>> interpret the "-e" option and writes something like "-e\nSEE ALSO",
>>> which causes rst2man to complain.
>>>
>>> I suspect the portable option here would be printf, even though Andrii
>>> had some concerns that we could pass a format specifier through the file
>>> names [0].
>>>
>>> Would this work on your setup?
>>>
>>>        $(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...
>>>
>>> Would that be acceptable?
>>
>> It works for me. Andrii originally suggested `echo -e`, but since `echo
>> -e` does not work in your environment let us use printf then. I will add
>> a comment about '%' in the bpftool man page name.
> 
> It's amazing how incompatible echo can be. But that aside, I have
> nothing against printf itself, but:
> 
> printf "%s" "whatever we want to print out"
> 
> seems like the way to go, similarly how you'd do it in your C code, no?

This won't really work :-(

-bash-4.4$ printf "%s" "\n\n"
\n\n-bash-4.4$ printf "\n\n"


-bash-4.4$

Looks like "\n" needs to be in format string to make a difference.


> 
>>
>>>
>>> [0]
>>> https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e
>>>
>>> Quentin
>>>

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 18:06             ` Yonghong Song
@ 2020-09-14 18:13               ` Andrii Nakryiko
  2020-09-14 18:20                 ` Yonghong Song
  0 siblings, 1 reply; 12+ messages in thread
From: Andrii Nakryiko @ 2020-09-14 18:13 UTC (permalink / raw)
  To: Yonghong Song
  Cc: Quentin Monnet, bpf, Networking, Alexei Starovoitov,
	Daniel Borkmann, Kernel Team, Andrii Nakryiko

On Mon, Sep 14, 2020 at 11:06 AM Yonghong Song <yhs@fb.com> wrote:
>
>
>
> On 9/14/20 10:55 AM, Andrii Nakryiko wrote:
> > On Mon, Sep 14, 2020 at 10:46 AM Yonghong Song <yhs@fb.com> wrote:
> >>
> >>
> >>
> >> On 9/14/20 10:23 AM, Quentin Monnet wrote:
> >>> On 14/09/2020 17:54, Yonghong Song wrote:
> >>>>
> >>>>
> >>>> On 9/14/20 9:46 AM, Yonghong Song wrote:
> >>>>>
> >>>>>
> >>>>> On 9/14/20 1:16 AM, Quentin Monnet 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?
> >>>>>
> >>>>> Thanks for the tip! I looked at the generated output again. My above
> >>>>> fix can silent the warning, but certainly not correct.
> >>>>>
> >>>>> With the following change, I captured the intermediate result of the
> >>>>> .rst file.
> >>>>>
> >>>>>     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 -n $(call see_also,$<) ) | tee
> >>>>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
> >>>>>
> >>>>> With below command,
> >>>>>       make clean && make bpftool-cgroup.8
> >>>>> I can get the new .rst file for bpftool-cgroup.
> >>>>>
> >>>>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
> >>>>>
> >>>>>        ID       AttachType      AttachFlags     Name
> >>>>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
> >>>>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
> >>>>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
> >>>>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
> >>>>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
> >>>>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
> >>>>> (8),\n\t**bpftool-struct_ops**\ (8)\n
> >>>>>
> >>>>> This sounds correct if we rst2man can successfully transforms '\n'
> >>>>> or '\t' to proper encoding in the man page.
> >>>>>
> >>>>> Unfortunately, with my version of rst2man, I got
> >>>>>
> >>>>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
> >>>>> Literal block ends without a blank line; unexpected unindent.
> >>>>> .sp
> >>>>> n SEE
> >>>>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
> >>>>>
> >>>>> .\" Generated by docutils manpage writer.
> >>>>>
> >>>>> The rst2man simply considered \n as 'n'. The same for '\t' and
> >>>>> this caused the issue.
> >>>>>
> >>>>> I did not find a way to fix the problem https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-3A__zoom.us_j_94864957378-3Fpwd-253DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09-26sa-3DD-26source-3Dcalendar-26ust-3D1600532408208000-26usg-3DAOvVaw3SJ0i8oz4ZM-2DGRb7hYkrYlyet&d=DwIDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=kEK7ScPMF-y-i8dli-or8wWEGREW5V4qPB7UqHqDnkg&s=Br0g0MFXxL_pJuDVTOY5UrmvfD2ru_6Uf_X_8Nr2Rhk&e= .
> >>>>
> >>>> The following change works for me.
> >>>>
> >>>> @@ -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)
> >>>> -bash-4.4$
> >>>>
> >>>> I will send revision 2 shortly.
> >>>
> >>> Thanks Yonghong, but this does not work on my setup :/. The version of
> >>> echo which is called on my machine from the Makefile does not seem to
> >>> interpret the "-e" option and writes something like "-e\nSEE ALSO",
> >>> which causes rst2man to complain.
> >>>
> >>> I suspect the portable option here would be printf, even though Andrii
> >>> had some concerns that we could pass a format specifier through the file
> >>> names [0].
> >>>
> >>> Would this work on your setup?
> >>>
> >>>        $(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...
> >>>
> >>> Would that be acceptable?
> >>
> >> It works for me. Andrii originally suggested `echo -e`, but since `echo
> >> -e` does not work in your environment let us use printf then. I will add
> >> a comment about '%' in the bpftool man page name.
> >
> > It's amazing how incompatible echo can be. But that aside, I have
> > nothing against printf itself, but:
> >
> > printf "%s" "whatever we want to print out"
> >
> > seems like the way to go, similarly how you'd do it in your C code, no?
>
> This won't really work :-(
>
> -bash-4.4$ printf "%s" "\n\n"
> \n\n-bash-4.4$ printf "\n\n"
>
>
> -bash-4.4$
>
> Looks like "\n" needs to be in format string to make a difference.
>

I just learned that %b was added specifically for that case:

$ printf "%b" "\n\n"


$

>
> >
> >>
> >>>
> >>> [0]
> >>> https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e
> >>>
> >>> Quentin
> >>>

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PATCH bpf-next] bpftool: fix build failure
  2020-09-14 18:13               ` Andrii Nakryiko
@ 2020-09-14 18:20                 ` Yonghong Song
  0 siblings, 0 replies; 12+ messages in thread
From: Yonghong Song @ 2020-09-14 18:20 UTC (permalink / raw)
  To: Andrii Nakryiko
  Cc: Quentin Monnet, bpf, Networking, Alexei Starovoitov,
	Daniel Borkmann, Kernel Team, Andrii Nakryiko



On 9/14/20 11:13 AM, Andrii Nakryiko wrote:
> On Mon, Sep 14, 2020 at 11:06 AM Yonghong Song <yhs@fb.com> wrote:
>>
>>
>>
>> On 9/14/20 10:55 AM, Andrii Nakryiko wrote:
>>> On Mon, Sep 14, 2020 at 10:46 AM Yonghong Song <yhs@fb.com> wrote:
>>>>
>>>>
>>>>
>>>> On 9/14/20 10:23 AM, Quentin Monnet wrote:
>>>>> On 14/09/2020 17:54, Yonghong Song wrote:
>>>>>>
>>>>>>
>>>>>> On 9/14/20 9:46 AM, Yonghong Song wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 9/14/20 1:16 AM, Quentin Monnet 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?
>>>>>>>
>>>>>>> Thanks for the tip! I looked at the generated output again. My above
>>>>>>> fix can silent the warning, but certainly not correct.
>>>>>>>
>>>>>>> With the following change, I captured the intermediate result of the
>>>>>>> .rst file.
>>>>>>>
>>>>>>>      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 -n $(call see_also,$<) ) | tee
>>>>>>> /tmp/tt | rst2man $(RST2MAN_OPTS) > $@
>>>>>>>
>>>>>>> With below command,
>>>>>>>        make clean && make bpftool-cgroup.8
>>>>>>> I can get the new .rst file for bpftool-cgroup.
>>>>>>>
>>>>>>> At the end of file /tmp/tt (changed bpftool-cgroup.rst), I see
>>>>>>>
>>>>>>>         ID       AttachType      AttachFlags     Name
>>>>>>> \n SEE ALSO\n========\n\t**bpf**\ (2),\n\t**bpf-helpers**\
>>>>>>> (7),\n\t**bpftool**\ (8),\n\t**bpftool-btf**\
>>>>>>> (8),\n\t**bpftool-feature**\ (8),\n\t**bpftool-gen**\
>>>>>>> (8),\n\t**bpftool-iter**\ (8),\n\t**bpftool-link**\
>>>>>>> (8),\n\t**bpftool-map**\ (8),\n\t**bpftool-net**\
>>>>>>> (8),\n\t**bpftool-perf**\ (8),\n\t**bpftool-prog**\
>>>>>>> (8),\n\t**bpftool-struct_ops**\ (8)\n
>>>>>>>
>>>>>>> This sounds correct if we rst2man can successfully transforms '\n'
>>>>>>> or '\t' to proper encoding in the man page.
>>>>>>>
>>>>>>> Unfortunately, with my version of rst2man, I got
>>>>>>>
>>>>>>> .IP "System Message: WARNING/2 (<stdin>:, line 146)"
>>>>>>> Literal block ends without a blank line; unexpected unindent.
>>>>>>> .sp
>>>>>>> n SEE
>>>>>>> ALSOn========nt**bpf**(2),nt**bpf\-helpers**(7),nt**bpftool**(8),nt**bpftool\-btf**(8),nt**bpftool\-feature**(8),nt**bpftool\-gen**(8),nt**bpftool\-iter**(8),nt**bpftool\-link**(8),nt**bpftool\-map**(8),nt**bpftool\-net**(8),nt**bpftool\-perf**(8),nt**bpftool\-prog**(8),nt**bpftool\-struct_ops**(8)n
>>>>>>>
>>>>>>> .\" Generated by docutils manpage writer.
>>>>>>>
>>>>>>> The rst2man simply considered \n as 'n'. The same for '\t' and
>>>>>>> this caused the issue.
>>>>>>>
>>>>>>> I did not find a way to fix the problem https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-3A__zoom.us_j_94864957378-3Fpwd-253DbXFRL1ZaRUxTbDVKcm9uRitpTXgyUT09-26sa-3DD-26source-3Dcalendar-26ust-3D1600532408208000-26usg-3DAOvVaw3SJ0i8oz4ZM-2DGRb7hYkrYlyet&d=DwIDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=kEK7ScPMF-y-i8dli-or8wWEGREW5V4qPB7UqHqDnkg&s=Br0g0MFXxL_pJuDVTOY5UrmvfD2ru_6Uf_X_8Nr2Rhk&e= .
>>>>>>
>>>>>> The following change works for me.
>>>>>>
>>>>>> @@ -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)
>>>>>> -bash-4.4$
>>>>>>
>>>>>> I will send revision 2 shortly.
>>>>>
>>>>> Thanks Yonghong, but this does not work on my setup :/. The version of
>>>>> echo which is called on my machine from the Makefile does not seem to
>>>>> interpret the "-e" option and writes something like "-e\nSEE ALSO",
>>>>> which causes rst2man to complain.
>>>>>
>>>>> I suspect the portable option here would be printf, even though Andrii
>>>>> had some concerns that we could pass a format specifier through the file
>>>>> names [0].
>>>>>
>>>>> Would this work on your setup?
>>>>>
>>>>>         $(QUIET_GEN)( cat $< ; printf $(call see_also,$<) ) | rst2man...
>>>>>
>>>>> Would that be acceptable?
>>>>
>>>> It works for me. Andrii originally suggested `echo -e`, but since `echo
>>>> -e` does not work in your environment let us use printf then. I will add
>>>> a comment about '%' in the bpftool man page name.
>>>
>>> It's amazing how incompatible echo can be. But that aside, I have
>>> nothing against printf itself, but:
>>>
>>> printf "%s" "whatever we want to print out"
>>>
>>> seems like the way to go, similarly how you'd do it in your C code, no?
>>
>> This won't really work :-(
>>
>> -bash-4.4$ printf "%s" "\n\n"
>> \n\n-bash-4.4$ printf "\n\n"
>>
>>
>> -bash-4.4$
>>
>> Looks like "\n" needs to be in format string to make a difference.
>>
> 
> I just learned that %b was added specifically for that case:
> 
> $ printf "%b" "\n\n"

Great! I learned some bash magic today... Will send v3.

> 
> 
> $
> 
>>
>>>
>>>>
>>>>>
>>>>> [0]
>>>>> https://lore.kernel.org/bpf/ca595fd6-e807-ac8e-f15f-68bfc7b7dbc4@isovalent.com/T/#m01bb298fd512121edd5e77a26ed5382c0c53939e
>>>>>
>>>>> Quentin
>>>>>

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2020-09-14 18:21 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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.