Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad.86@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/wireshark: fix support for lua
Date: Mon, 28 Sep 2026 10:42:53 +0200	[thread overview]
Message-ID: <arooOH-qmgHdt6PS@windsurf> (raw)
In-Reply-To: <20260928074239.24304-1-francois.perrad.86@gmail.com>

On Mon, Sep 28, 2026 at 09:42:38AM +0200, Francois Perrad wrote:
> since 4.4.0, support for Lua 5.3 and 5.4 has been added,
> and support for Lua 5.1 and 5.2 has been removed.
> see https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html

Is this fixing a build issue?

I did a build locally, and I see cmake taking 100% CPU time at the
step:

-- Considering the following Lua versions: 5.4;5.3

is this what you are seeing as well?

Since this is a fix, please add a reference to the Buildroot commit
being fixed:

Fixes: 49fa20e6678ee32e4b26979f5cb4d149876fbedd ("package/wireshark: bump to latest upstream stable v4.4.9")

Thanks!

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

  reply	other threads:[~2026-09-28  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  7:42 [Buildroot] [PATCH] package/wireshark: fix support for lua Francois Perrad
2026-09-28  8:42 ` Thomas Petazzoni via buildroot [this message]
2026-09-28 11:23   ` François PERRAD

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=arooOH-qmgHdt6PS@windsurf \
    --to=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=francois.perrad.86@gmail.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