DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: "bugzilla@dpdk.org" <bugzilla@dpdk.org>,
	Luca Boccassi <bluca@debian.org>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-dev] [Bug 303] meson-0.51.0 isn't building docs
Date: Wed, 3 Jul 2019 11:14:24 +0000	[thread overview]
Message-ID: <DB6PR0501MB21678099EE44EC66CFF67967D7FB0@DB6PR0501MB2167.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <bug-303-3@http.bugs.dpdk.org/>

CC-ing Luca

0.50.0 seems to be the first broken version.

Is this related to https://github.com/mesonbuild/meson/issues/4717?

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of bugzilla@dpdk.org
> Sent: Wednesday, July 3, 2019 10:17 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [Bug 303] meson-0.51.0 isn't building docs
> 
<removed>
> 
>             Bug ID: 303
>            Summary: meson-0.51.0 isn't building docs
>            Product: DPDK
>            Version: 19.08
>           Hardware: All
>                 OS: All
>             Status: CONFIRMED
>           Severity: normal
>           Priority: Normal
>          Component: meson
>           Assignee: dev@dpdk.org
>           Reporter: alialnu@mellanox.com
>   Target Milestone: ---
> 
<removed>
> 
> Latest meson version 0.51.0 isn't building the documentation. Version 0.47.1
> works ok for me.
<removed>
> <pre>
> $ meson -Denable_docs=true build
> </pre>
<removed> 
> <pre>
> $ ninja -C build
> </pre>
<removed>
> No documentation will be built:
> <pre>
> $ find build/doc/build/doc/
> 
> build/doc/api
> build/doc/api/doxy-api.conf
> build/doc/guides
> </pre>
> 

-Ali

           reply	other threads:[~2019-07-03 11:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-303-3@http.bugs.dpdk.org/>]

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=DB6PR0501MB21678099EE44EC66CFF67967D7FB0@DB6PR0501MB2167.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=bluca@debian.org \
    --cc=bugzilla@dpdk.org \
    --cc=ci@dpdk.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).