Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] lua: fix pkg-config file
Date: Wed, 02 Aug 2017 10:04:28 +0200	[thread overview]
Message-ID: <1501661068.1978.11.camel@embedded.rocks> (raw)
In-Reply-To: <20170801190840.457a6f6d@windsurf.home>

Hi Thomas,

On Tue, 2017-08-01 at 19:08 +0200, Thomas Petazzoni wrote:
> 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.

It is an autobuilder issue indeed, but it was not detected the date I
wrote the patch. The autobuilder issues concerning swupdate until that
date where Lua 5.1/LuaJIT related. I noticed the issue using the Linaro
 Toolchain for armhf.

There is now a report of an autobuilder from yesterday:
http://autobuild.buildroot.net/results/1c3/1c349cc5904868e4def292b9fbfa
164828e46156/

Not all toolchains are producing the issue (only glibc ones?):

                armv5-ctng-linux-gnueabi [ 1/47]: FAILED
              armv7-ctng-linux-gnueabihf [ 2/47]: FAILED
                        br-aarch64-glibc [ 3/47]: FAILED
                           br-arcle-hs38 [ 4/47]: OK
                            br-arm-basic [ 5/47]: OK
                  br-arm-cortex-a9-glibc [ 6/47]: FAILED
                   br-arm-cortex-a9-musl [ 7/47]: OK
                             br-arm-full [ 9/47]: OK
                      br-arm-full-static [11/47]: OK
                   br-i386-pentium4-full [13/47]: OK
                br-i386-pentium-mmx-musl [14/47]: OK
                      br-m68k-68040-full [16/47]: OK
                    br-microblazeel-full [17/47]: OK
                 br-mips32r6-el-hf-glibc [18/47]: FAILED
                      br-mips64-n64-full [19/47]: OK
                 br-mips64r6-el-hf-glibc [20/47]: FAILED

J?rg

  reply	other threads:[~2017-08-02  8:04 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 ` [Buildroot] [PATCH 1/2] lua: fix pkg-config file Thomas Petazzoni
2017-08-02  8:04   ` Jörg Krause [this message]
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=1501661068.1978.11.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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