From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] lua interpreter choice?
Date: Wed, 30 Jul 2014 12:31:56 -0500 [thread overview]
Message-ID: <20140730123156.0a636f01@core2quad.morethan.org> (raw)
In-Reply-To: <CANxTyt6-4j70z297t4VsaqKGosnTdWarc5fBVa3vVORmXnWMFQ@mail.gmail.com>
On Wed, 30 Jul 2014 12:59:10 -0400
Danomi Manchego <danomimanchego123@gmail.com> wrote:
> All,
>
> With older buildroot releases, I was able to have lua and luajit side
> by side. After upgrading, I can *still* select both in the
> menuconfig, but compiling give me:
>
> 'package/luajit/luajit.mk:75: *** Configuration error: both "luajit"
> and "lua" are selected as providers for virtual package
> "luainterpreter". Only one provider can be selected at a time. Please
> fix your configuration. Stop.'
>
> I'm okay (I think) with disabling lua, as I don't *think* I need the
> lighttpd "Lua support" option, which was forcing lua to be on. If the
> build will not allow both to be on then I'm wondering if, just as
> libjpeg and jpeg-turbo are values for the "jpeg support" choice, if
> the lua/luajit selection should be a choice rather than two separately
> selectable packages?
>
If using Lua 5.2 version code, you only need LuaJit, LuaJit-2.0.3 runs
Lua 5.2 code.
If using Lua 5.3 version code, then you need Lua-5.3 or Lua-5.2
compatability changes to your Lua 5.3 code.
I am not sure just how that relationship is handled in Buildroot.
Mike
> Danomi -
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2014-07-30 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:59 [Buildroot] lua interpreter choice? Danomi Manchego
2014-07-30 17:31 ` Mike Zick [this message]
2014-07-30 18:47 ` François Perrad
2014-07-30 18:51 ` Danomi Manchego
2014-07-30 21:40 ` Thomas Petazzoni
2014-07-30 22:34 ` Danomi Manchego
2014-07-30 23:11 ` Yann E. MORIN
2014-07-30 23:19 ` Yann E. MORIN
2014-07-30 23:49 ` Danomi Manchego
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=20140730123156.0a636f01@core2quad.morethan.org \
--to=minimod@morethan.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox