From: "Guo Hongruan" <camelguo@gmail.com>
To: "Guo Hongruan" <camelguo@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: building piccontrol - 0.4 failed due to lack of liblua5.1.a
Date: Sun, 31 Jan 2010 13:56:58 +0800 [thread overview]
Message-ID: <op.u7dus8qwmn1qzu@camelguo> (raw)
In-Reply-To: <op.u7dt8jyhmn1qzu@camelguo>
在 Sun, 31 Jan 2010 13:44:33 +0800,Guo Hongruan <camelguo@gmail.com> 写道:
> 在 Sun, 31 Jan 2010 13:22:16 +0800,Khem Raj <raj.khem@gmail.com> 写道:
>
>> in your build tree check where liblua5.1.a is installed and then
>> go from there.
>
> instead of liblue5.1.a, I found libua.a on my build tree. Maybe it is
> the cause of the error.
>
> ./armv5te-oe-linux-gnueabi/lib/liblua.a
>
I found it, it is caused by
1. lua5.1_5.1.4.bb install lib/liblua. to staging directory;
2. but piccoontrol_0.4.bb tries to link liblua5.1.a, which name is
liblua.a.
20 LDFLAGS += " ${STAGING_LIBDIR}/liblua5.1.a -lpthread -lm -ldl "
changing piccontrol_0.4.bb may correct the error.
diff --git a/recipes/piccontrol/piccontrol_0.4.bb
b/recipes/piccontrol/piccontrol_0.4.bb
index cfdef98..854f156 100644
--- a/recipes/piccontrol/piccontrol_0.4.bb
+++ b/recipes/piccontrol/piccontrol_0.4.bb
@@ -17,7 +17,7 @@ inherit update-rc.d
INITSCRIPT_NAME = "piccontrol"
INITSCRIPT_PARAMS = "defaults"
-LDFLAGS += " ${STAGING_LIBDIR}/liblua5.1.a -lpthread -lm -ldl "
+LDFLAGS += " ${STAGING_LIBDIR}/liblua.a -lpthread -lm -ldl "
CFLAGS += " -I${STAGING_INCDIR}/lua5.1 "
do_install() {
--
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com
next prev parent reply other threads:[~2010-01-31 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 3:01 building piccontrol - 0.4 failed due to lack of liblua5.1.a Guo Hongruan
2010-01-31 5:22 ` Khem Raj
2010-01-31 5:43 ` Guo Hongruan
2010-01-31 5:44 ` Guo Hongruan
2010-01-31 5:56 ` Guo Hongruan [this message]
2010-01-31 6:14 ` Holger Hans Peter Freyther
2010-01-31 6:22 ` Guo Hongruan
2010-03-28 11:56 ` Stefan Schmidt
2010-01-31 9:34 ` Petr Štetiar
2010-01-31 16:53 ` Tim Ellis
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=op.u7dus8qwmn1qzu@camelguo \
--to=camelguo@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.