From: Ross Burton <Ross.Burton@arm.com>
To: "changqing.li@windriver.com" <changqing.li@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH V3] lua: upgrade from 5.4.8 to 5.5.0
Date: Tue, 3 Mar 2026 15:16:28 +0000 [thread overview]
Message-ID: <FEAC2A3F-4384-4D3C-B9CE-FDA23332604B@arm.com> (raw)
In-Reply-To: <20260227070858.2687898-1-changqing.li@windriver.com>
Hi,
> On 27 Feb 2026, at 07:08, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
> Refer [1], PLATS linux-readline is moved, and readline is changed to
> load dynamically, keep readline as PACKAGECONFIG to allow user to remove
> readline dependency.
As is traditional with people using dlopen(), this is now broken…
Lua defaults to dlopen() support being enabled (LUA_USE_DLOPEN is defined on linux) and the readline library is set to libreadline.so <http://libreadline.so/>.
So the PACKAGECONFIG is not doing the right thing anymore: having readline in the sysroot doesn’t change the build, and has no impact on the runtime packages.
The obvious answer is to change the PACKAGECONFIG to “,,,readline” so that there’s still an option that has the effect of enabling readline in lua, but that also won’t work as the on-disk file isn’t called libreadline.so <http://libreadline.so/> unless you install the -dev package…. This means we should also set LUA_READLINELIB to "libreadline.so.8”.
Bonus points for adding readline as a build dependency and looking up what the libreadline.so <http://libreadline.so/> symlink resolves to, but I don’t expect the readline soname to change in the near future so this can be considered overkill.
Ross
next prev parent reply other threads:[~2026-03-03 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 2:46 [PATCH V2] lua: upgrade from 5.4.8 to 5.5.0 Changqing Li
2026-02-26 13:37 ` [OE-core] " Ross Burton
2026-02-27 7:07 ` Changqing Li
2026-02-27 7:08 ` [PATCH V3] " Changqing Li
2026-03-03 15:16 ` Ross Burton [this message]
2026-03-04 7:23 ` [OE-core] " Changqing Li
2026-03-04 17:58 ` Ross Burton
2026-03-05 10:54 ` [PATCH V4] " Changqing Li
2026-03-06 10:18 ` [OE-core] " Mathieu Dubois-Briand
2026-03-09 6:07 ` [PATCH V5] " Changqing Li
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=FEAC2A3F-4384-4D3C-B9CE-FDA23332604B@arm.com \
--to=ross.burton@arm.com \
--cc=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.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