Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libnvme: fix python build
Date: Sat, 4 Nov 2023 21:50:19 +0100	[thread overview]
Message-ID: <20231104215019.26617084@windsurf> (raw)
In-Reply-To: <20231002165345.346937-1-fontaine.fabrice@gmail.com>

On Mon,  2 Oct 2023 18:53:45 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fix the following build failure raised since the addition of the package
> in commit cd7bc6b1c410514765c51821bb8d843f136fea4a:
> 
> Program python3 found: YES (/home/autobuild/autobuild/instance-6/output-1/host/bin/python3)
> Program swig found: NO
> 
> ../output-1/build/libnvme-1.5/libnvme/meson.build:15:11: ERROR: Program 'swig' not found or not executable
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/3cb05b4939eb7d1ce0460088c365402ffcd6b13b
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/libnvme/libnvme.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Sorry, I did not notice this patch from you, and merged a similar patch
from Giulio submitted later. Sorry about this :/

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-11-04 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 16:53 [Buildroot] [PATCH 1/1] package/libnvme: fix python build Fabrice Fontaine
2023-10-02 17:20 ` Giulio Benetti
2023-11-04 20:50 ` Thomas Petazzoni via buildroot [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:
  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=20231104215019.26617084@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=thomas.petazzoni@bootlin.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