From: Ghislain Hachey <ghachey.lists@gmail.com>
To: development@lists.ipfire.org
Subject: Re: LuaJIT Panic on IPFire
Date: Tue, 29 Jul 2014 16:13:04 +0800 [thread overview]
Message-ID: <53D75790.2080605@gmail.com> (raw)
In-Reply-To: <1404724703.19419.14.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
Hi,
I am trying to achieve something here I don't know if this is supported.
I've built a custom addon for ntopng, a traffic monitoring tool which
makes use of LuaJIT for its web UI scripting language (which is great
for embedded devices). When starting the service on my home IPFire I
quickly get the following error message.
PANIC: unprotected error in call to Lua API (runtime code generation
failed, restricted kernel?)
Which leads me to think that a JIT is not supported in the kernel
configuration of IPFire, or am I way off? This is a tool I'd really like
to get working on my IPFire, any ideas?
Regards,
--
GH
next prev parent reply other threads:[~2014-07-29 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 9:45 IPFire Building Packages Ghislain Hachey
2014-07-05 14:15 ` Michael Tremer
2014-07-05 23:01 ` Ghislain Hachey
2014-07-06 8:57 ` Michael Tremer
2014-07-06 9:44 ` Ghislain Hachey
2014-07-07 9:18 ` Michael Tremer
2014-07-08 10:35 ` MySQL 5.6.19 Sascha Kilian
2014-07-08 13:10 ` Sascha Kilian
2014-07-29 8:13 ` Ghislain Hachey [this message]
2014-07-29 8:27 ` LuaJIT Panic on IPFire Arne Fitzenreiter
2014-07-07 8:49 ` IPFire Building Packages Ghislain Hachey
2014-07-07 9:22 ` Michael Tremer
2014-07-07 9:50 ` Ghislain Hachey
2014-07-07 10:35 ` Michael Tremer
2014-07-07 10:48 ` Ghislain Hachey
2014-07-11 4:18 ` Ghislain Hachey
2014-07-06 8:51 ` Ghislain Hachey
2014-07-06 9:03 ` Michael Tremer
[not found] <mailman.1.1406628001.22194.development@lists.ipfire.org>
2014-07-30 7:37 ` LuaJIT Panic on IPFire Ghislain Hachey
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=53D75790.2080605@gmail.com \
--to=ghachey.lists@gmail.com \
--cc=development@lists.ipfire.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