All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] swupdate: added a warning for LuaJIT/Lua 5.1
Date: Fri, 29 Jul 2016 18:38:53 +0200	[thread overview]
Message-ID: <1469810333.3805.16.camel@embedded.rocks> (raw)
In-Reply-To: <8fc5a199-611c-d45e-e655-cc81e288aa9c@yelloz.me>

On Fr, 2016-07-29 at 09:32 -0700, Jordan Yelloz wrote:
> On 07/29/2016 09:20 AM, J?rg Krause wrote:
> > 
> > On So, 2016-07-24 at 16:27 -0700, Jordan Yelloz wrote:
> > > 
> > > Signed-off-by: Jordan Yelloz <jordan@yelloz.me>
> > > ---
> > > ?package/swupdate/Config.in | 6 ++++++
> > > ?1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/package/swupdate/Config.in
> > > b/package/swupdate/Config.in
> > > index 85dde4eb0bc5..046903de87f5 100644
> > > --- a/package/swupdate/Config.in
> > > +++ b/package/swupdate/Config.in
> > > @@ -55,6 +55,12 @@ config BR2_PACKAGE_SWUPDATE_INSTALL_WEBSITE
> > > ?	??This is necessary if you want to run swupdate with the
> > > embedded
> > > ?	??webserver and do not provide an own website to be
> > > installed to
> > > ?	??/var/www/swupdate.
> > > +
> > > +if BR2_PACKAGE_LUA_5_1 || BR2_PACKAGE_LUAJIT
> > > +comment "swupdate cannot use CONFIG_HANDLER_IN_LUA with Lua API
> > > <
> > > 5.2."
> > > +comment "Lua parsers and pre/post-install hooks should still
> > > work.????"
> > > +endif
> > > +
> > 
> > I would prefer to put this as a note in the help text.
> > 
> 
> Ok, I can move it there.
> 
> > 
> > Do you know where this restriction comes from? Why does the Lua
> > handlers does not work? Did you tell upstream about the issue?
> > AFAIK
> > swupate should work with Lua 5.1 - 5.3, but I did not checked.
> 
> The handlers incompatibility is because of the Lua C API changes from
> 5.1 to 5.2.
> I've done some testing earlier this week and it turns out you can
> actually include the compat53 C files
> (<https://github.com/keplerproject/lua-compat-5.3/tree/master/c-api>)
> into swupdate's core/handler.c if you really want and the lua
> handlers
> feature will build and work successfully with Lua 5.1 and LuaJIT
> (though
> I have done very limited testing).
> 
> I started writing a patch for swupdate but I currently have no use
> for
> the handlers in lua and don't have the time to integrate it into
> swupdate's build system so it's on hold.

Maybe you could report it on the swupdates mailing list. Maybe Stefano
Babic can help you with the patch.

J?rg

  reply	other threads:[~2016-07-29 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 23:27 [Buildroot] [PATCH 0/4] swupdate: allow configuring with LuaJIT Jordan Yelloz
2016-07-24 23:27 ` [Buildroot] [PATCH 1/4] swupdate: allowed luajit to enable HAVE_LUA Jordan Yelloz
2016-07-25  7:31   ` Thomas Petazzoni
2016-07-25 16:46     ` Jordan Yelloz
2016-10-25 11:56   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 2/4] swupdate: updated lua check for libconfig Jordan Yelloz
2016-07-29 16:15   ` Jörg Krause
2016-10-25 19:36   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 3/4] swupdate: improved help text for Lua support Jordan Yelloz
2016-07-25  7:32   ` Thomas Petazzoni
2016-07-25 16:36     ` Jordan Yelloz
2016-07-29 16:14       ` Jörg Krause
2016-07-29 20:28         ` Jordan Yelloz
2016-10-25 19:43   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 4/4] swupdate: added a warning for LuaJIT/Lua 5.1 Jordan Yelloz
2016-07-29 16:20   ` Jörg Krause
2016-07-29 16:32     ` Jordan Yelloz
2016-07-29 16:38       ` Jörg Krause [this message]
2016-10-25 19:43     ` Thomas Petazzoni

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=1469810333.3805.16.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=buildroot@busybox.net \
    /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.