Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/3] uhttpd: new package
Date: Sat, 5 Nov 2016 14:20:01 +0100	[thread overview]
Message-ID: <20161105142001.661fc196@free-electrons.com> (raw)
In-Reply-To: <1476702145-25280-2-git-send-email-Rahul.Jain@imgtec.com>

Hello,

On Mon, 17 Oct 2016 16:32:24 +0530, Rahul Jain wrote:

> +ifeq ($(BR2_PACKAGE_LUAINTERPRETER_ABI_VERSION),"5.1")
> +ifeq ($(BR2_PACKAGE_LUA),y)
> +UHTTPD_DEPENDENCIES += lua
> +else ifeq ($(BR2_PACKAGE_LUAJIT),y)
> +UHTTPD_DEPENDENCIES += luajit

It doesn't build with LuaJIT:

[ 35%] Linking C shared module uhttpd_lua.so
/home/thomas/projets/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.8.5/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld: cannot find -llua
collect2: error: ld returned 1 exit status

So I've modified  your patch to only use Lua. If you want to re-enable
LuaJIT support, could you fix the issue and send a follow-up patch?

Applied to next with this issue fixed.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-05 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 11:02 [Buildroot] [PATCH v4 1/3] ustream-ssl: new package Rahul Jain
2016-10-17 11:02 ` [Buildroot] [PATCH v4 2/3] uhttpd: " Rahul Jain
2016-11-05 13:20   ` Thomas Petazzoni [this message]
2016-10-17 11:02 ` [Buildroot] [PATCH v4 3/3] DEVELOPERS: add entry for uhttpd and ustream-ssl Rahul Jain
2016-11-05 13:20   ` Thomas Petazzoni
2016-10-17 20:03 ` [Buildroot] [PATCH v4 1/3] ustream-ssl: new package Samuel Martin
2016-10-18  7:41   ` Rahul Jain
2016-11-05 13:19 ` Thomas Petazzoni
2016-12-04 14:07 ` 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=20161105142001.661fc196@free-electrons.com \
    --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