All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 374] Meson build failure due to libibverbs-dev upgrade (version=45mlnx1-1.45101)
Date: Mon, 02 Dec 2019 17:21:47 +0000	[thread overview]
Message-ID: <bug-374-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=374

            Bug ID: 374
           Summary: Meson build failure due to libibverbs-dev upgrade
                    (version=45mlnx1-1.45101)
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: dharmik.thakkar@arm.com
  Target Milestone: ---

I am seeing DPDK (19.11-rc2) meson build issue with upgrading libibverbs-dev to
version=45mlnx1-1.45101 on both x86 and Aarch64 platforms.
The issue doesn’t occur with Make. When I downgrade it to
version=17.1-1ubuntu0.2, the issue gets resolved.

Also, it looks like Make and meson have different rules in DPDK.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2019-12-02 17:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-374-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 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.