From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem build haserl with lua support
Date: Thu, 31 Jan 2013 12:52:34 +0100 [thread overview]
Message-ID: <20130131125234.166475a7@skate> (raw)
In-Reply-To: <1359630353.9888.41.camel@john-ubu>
Dear john,
On Thu, 31 Jan 2013 11:05:53 +0000, john wrote:
> Hi,
>
> I'm using Buildroot 2012.05 and am trying to configure haserl v0.9.X
> with lua support. I select the lua intrepreter and have not selected lua
> library modules.
You may want to update your Buildroot version, because I think the
problem have been fixed:
https://bugs.busybox.net/show_bug.cgi?id=5354
See commit 684f208ec 'lua: don't be fancy when creating shared library'.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-31 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 11:05 [Buildroot] Problem build haserl with lua support john
2013-01-31 11:52 ` Thomas Petazzoni [this message]
2013-02-01 17:30 ` john
2013-02-02 10:47 ` 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=20130131125234.166475a7@skate \
--to=thomas.petazzoni@free-electrons.com \
--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