DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Murrell, Brian" <brian.murrell@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	 Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] Error building documentation
Date: Mon, 15 Feb 2021 09:27:02 +0100	[thread overview]
Message-ID: <CAJFAV8wgP+fHNeQ8B0yrnGo5=EFwPSJZ+OLzczhZ4+SmW87BUQ@mail.gmail.com> (raw)
In-Reply-To: <4fb0e6538901f9d63d959b8e82d53b7373703219.camel@intel.com>

On Mon, Feb 8, 2021 at 2:44 PM Murrell, Brian <brian.murrell@intel.com> wrote:
> When I add "-Denable_docs=true" to my DPDK 20.11 build commandline I
> get a build error:
> FAILED: doc/guides/html
> /usr/bin/python3.6 ../buildtools/call-sphinx-build.py /bin/sphinx-build
> 20.11.0 /home/brian/daos/rpm/dpdk/_topdir/BUILD/dpdk-20.11/doc/guides
> /home/brian/daos/rpm/dpdk/_topdir/BUILD/dpdk-20.11/build/doc/guides
> Traceback (most recent call last):
>   File "../buildtools/call-sphinx-build.py", line 22, in <module>
>     if StrictVersion(ver) >= StrictVersion('1.7'):
>   File "/usr/lib64/python3.6/distutils/version.py", line 40, in
> __init__
>     self.parse(vstring)
>   File "/usr/lib64/python3.6/distutils/version.py", line 137, in parse
>     raise ValueError("invalid version number '%s'" % vstring)
> ValueError: invalid version number 'these.'
> Is this a known issue?

I guess you use an old sphinx version, like maybe sphinx on RHEL7 ?

Example on my rhel7:

$ sphinx-build --version
Sphinx v1.1.3
* with -a, write all files.
* with filenames, write these.

Afaics, we require sphinx >= 1.7 for building the documentation.

David Marchand

      reply	other threads:[~2021-02-15  8:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 13:43 Murrell, Brian
2021-02-15  8:27 ` David Marchand [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJFAV8wgP+fHNeQ8B0yrnGo5=EFwPSJZ+OLzczhZ4+SmW87BUQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=brian.murrell@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \


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