DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] examples/power: fix FreeBSD meson lib dependency
Date: Fri, 12 Jul 2019 16:23:19 -0700	[thread overview]
Message-ID: <20190712162319.454ce2db@hermes.lan> (raw)
In-Reply-To: <20190712090651.11824-1-david.hunt@intel.com>

On Fri, 12 Jul 2019 10:06:51 +0100
David Hunt <david.hunt@intel.com> wrote:

> Samples apps that depend on the power library should not build if
> the power library is not present. So now the following apps will
> check to see if it's built, else skip building.
> * l3fwd-pwer
> * vm_power_manager
> * guest_cli
> 
> Fixes: e0130788576f ("examples/power: support meson/ninja build")
> Fixes: 89f0711f9ddf ("examples: build some samples with meson")
> Signed-off-by: David Hunt <david.hunt@intel.com>

Still seeing failures in build today.

My patches (not related) today failed intel-compilation...

*Meson Build Failed #1:
OS: FreeBSD12-64
Target:build-gcc-static
Has header "linux/virtio_scsi.h" : NO
Message: Skipping example "vhost_scsi"
Library virt found: YES
Dependency jansson found: YES (cached)

examples/meson.build:88:4: ERROR: Problem encountered: Missing dependency "power" for example "vm_power_manager"

A full log can be found at /tmp/FreeBSD12-64_K19.02_GCC7.3.0/x86_64-native-bsdapp-gcc/f76f15ed805042438074e510f781c48d/dpdk/build-gcc-static/meson-logs/meson-log.txt
ninja -C build-gcc-static
ninja: Entering directory `build-gcc-static'
ninja: error: loading 'build.ninja': No such file or directory
--
Has header "linux/virtio_scsi.h" : NO
Message: Skipping example "vhost_scsi"
Library virt found: YES
Dependency jansson found: YES (cached)

examples/meson.build:88:4: ERROR: Problem encountered: Missing dependency "power" for example "vm_power_manager"

A full log can be found at /tmp/FreeBSD12-64_K19.02_GCC7.3.0/x86_64-native-bsdapp-gcc/f76f15ed805042438074e510f781c48d/dpdk/build-gcc-shared/meson-logs/meson-log.txt
ninja -C build-gcc-shared
ninja: Entering directory `build-gcc-shared'
ninja: error: loading 'build.ninja': No such file or directory

  parent reply	other threads:[~2019-07-12 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  9:06 David Hunt
2019-07-12  9:22 ` Bruce Richardson
2019-07-12  9:28   ` Ferruh Yigit
2019-07-12 23:23 ` Stephen Hemminger [this message]
2019-07-15  8:51   ` Hunt, David

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=20190712162319.454ce2db@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /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).