DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <bugzilla@dpdk.org>
Cc: <dev@dpdk.org>
Subject: Re: [DPDK/core Bug 1547] Build fails on FreeBSD 14.0
Date: Wed, 18 Sep 2024 09:31:19 +0100	[thread overview]
Message-ID: <ZuqP10ntN4FzrVbq@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <bug-1547-3-uIPuC87SN1@http.bugs.dpdk.org/>

On Wed, Sep 18, 2024 at 01:51:18AM +0000, bugzilla@dpdk.org wrote:
>    [1]Stephen Hemminger changed [2]bug 1547
> 
>       What      Removed     Added
>    Status     UNCONFIRMED RESOLVED
>    Resolution ---         INVALID
> 
>    [3]Comment # 1 on [4]bug 1547 from [5]Stephen Hemminger
> Missing elftools on the build VM

Thanks seems like something that should be caught earlier at the configure
stage. I thought that meson checks for pyelftools - is it the python
package or the underlying C library that was missing?

/Bruce

  reply	other threads:[~2024-09-18  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  1:49 bugzilla
2024-09-18  1:51 ` bugzilla
2024-09-18  8:31   ` Bruce Richardson [this message]
2024-09-18 15:08     ` Stephen Hemminger

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=ZuqP10ntN4FzrVbq@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=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 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).