From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] lua: fix pkg-config file
Date: Tue, 1 Aug 2017 19:08:40 +0200 [thread overview]
Message-ID: <20170801190840.457a6f6d@windsurf.home> (raw)
In-Reply-To: <20170731211800.5888-1-joerg.krause@embedded.rocks>
Hello,
On Mon, 31 Jul 2017 23:17:59 +0200, J?rg Krause wrote:
> When Lua is linked with additional libraries, these libraries should go
> into the pkg-config file as well.
>
> Otherwise, linking swupdate with the lua library fails:
>
> ```
> /home/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/liblua.so: undefined reference to `dlopen'
> /home/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/liblua.so: undefined reference to `dlclose'
> /home/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/liblua.so: undefined reference to `dlerror'
> /home/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/liblua.so: undefined reference to `dlsym'
> ```
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
Is this fixing an autobuilder issue ? I guess it should fix the ones
you mention in PATCH 2/2, but obviously only for the supported Lua
versions.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-01 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 21:17 [Buildroot] [PATCH 1/2] lua: fix pkg-config file Jörg Krause
2017-07-31 21:18 ` [Buildroot] [PATCH 2/2] swupdate: support for Lua 5.1 is broken Jörg Krause
2017-08-01 17:10 ` Thomas Petazzoni
2017-08-02 6:42 ` Jörg Krause
2017-08-02 7:46 ` Jörg Krause
2017-08-10 12:51 ` Arnout Vandecappelle
2017-08-01 17:08 ` Thomas Petazzoni [this message]
2017-08-02 8:04 ` [Buildroot] [PATCH 1/2] lua: fix pkg-config file Jörg Krause
2017-09-05 21:52 ` Peter Korsgaard
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=20170801190840.457a6f6d@windsurf.home \
--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 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.