All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clayton Casciato <majortomtosourcecontrol@gmail.com>
To: Scott Murray <scott.murray@konsulko.com>
Cc: Yash.Shinde@windriver.com, rybczynska@gmail.com,
	yocto-patches@lists.yoctoproject.org
Subject: Re: [meta-security][PATCH v2 1/1] suricata: update 7.0.13 -> 8.0.4
Date: Wed, 22 Apr 2026 21:46:55 -0600	[thread overview]
Message-ID: <edb8ba0d-e084-4e2b-a072-bbfee949f582@gmail.com> (raw)
In-Reply-To: <5500aef7-608d-4ae4-afab-5c816d255031@gmail.com>

> It looks like the Lua 5.5.0 upgrade in oe-core has non-trivially broken
> the 8.0.x suricata build.  There's a somewhat straightforward issue with
> a new argument to lua_newstate, but after that there are link errors that
> the more I poked around the more I'm thinking there's some oddness wrt 
> their vendoring a copy of Lua (5.4.8) for the Rust side of things.  I
> don't see any signs of the build process for the .c files under src 
> pointing at that source, but then AFAICT everything kind of gets lumped
> together when linking the final suricata binary...  If you have the time
> to try to untangle this, please do so, as I cannot guarantee that I get 
> to it in the next week or two.
>@
> Thanks,
>@
> Scott

Thanks for the hint, Scott!

It appears an external Lua implementation is not required at build time.

I instead configured a variable ("SURICATA_LUA_SYS_HEADER_DST") for v2: 
https://lists.yoctoproject.org/g/yocto-patches/topic/meta_security_patch_v2_0_1/118966848
https://lists.yoctoproject.org/g/yocto-patches/topic/meta_security_patch_v2_1_1/118966849

Clayton Casciato


      reply	other threads:[~2026-04-23  3:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  3:40 [meta-security][PATCH v2 1/1] suricata: update 7.0.13 -> 8.0.4 Clayton Casciato
2026-04-23  3:46 ` Clayton Casciato [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=edb8ba0d-e084-4e2b-a072-bbfee949f582@gmail.com \
    --to=majortomtosourcecontrol@gmail.com \
    --cc=Yash.Shinde@windriver.com \
    --cc=rybczynska@gmail.com \
    --cc=scott.murray@konsulko.com \
    --cc=yocto-patches@lists.yoctoproject.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.