From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 2/3] lutok: new package
Date: Fri, 12 Jun 2015 21:45:09 +0200 [thread overview]
Message-ID: <20150612214509.08728a82@free-electrons.com> (raw)
In-Reply-To: <20150612213419.15566320@free-electrons.com>
Hello,
On Fri, 12 Jun 2015 21:34:19 +0200, Thomas Petazzoni wrote:
> Both the lutok and kyua packages after --without-atf ? Why so ? You add
> the atf package as the first patch, and then it isn't used in follow-up
> patches ?
Ok, --without-atf is not about ATF support, but about build ATF-based
tests. I've added a comment to explain this.
> > +# liblua uses dlopen when dynamically linked
> > +ifneq ($(BR2_STATIC_LIBS),y)
>
> ifeq ($(BR2_STATIC_LIBS),)
Actually, I was able to build without adding -ldl, so I'm not sure why
it is needed. We'll see what the autobuilders have to say, unless you
have more details about the specific configuration that was causing
problems.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-12 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 22:51 [Buildroot] [PATCH v5 0/3] kyua: new package and dependencies Sebastien Bourdelin
2015-06-11 22:51 ` [Buildroot] [PATCH v5 1/3] atf: new package Sebastien Bourdelin
2015-06-12 19:59 ` Thomas Petazzoni
2015-06-11 22:51 ` [Buildroot] [PATCH v5 2/3] lutok: " Sebastien Bourdelin
2015-06-12 19:34 ` Thomas Petazzoni
2015-06-12 19:45 ` Thomas Petazzoni [this message]
2015-06-12 23:04 ` Arnout Vandecappelle
2015-06-12 19:59 ` Thomas Petazzoni
2015-06-11 22:51 ` [Buildroot] [PATCH v5 3/3] kyua: " Sebastien Bourdelin
2015-06-12 20:02 ` Thomas Petazzoni
2015-06-12 23:17 ` Arnout Vandecappelle
2015-06-13 10:45 ` 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=20150612214509.08728a82@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