From: "Guo Hongruan" <camelguo@gmail.com>
To: openembeded-devel <openembedded-devel@lists.openembedded.org>
Cc: tim.ellis@foonas.org
Subject: building piccontrol - 0.4 failed due to lack of liblua5.1.a
Date: Sun, 31 Jan 2010 11:01:05 +0800 [thread overview]
Message-ID: <op.u7dmmldamn1qzu@camelguo> (raw)
Hi guys,
I tried to build MACHINE=tsx09 DISTRO=micro LIBC=glibc, but failed when
building picontrol. The error is the following:
NOTE: make -j 4 -e MAKEFLAGS=
ccache arm-oe-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mthumb
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
-I/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include/lua5.1
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-c -o piccontrol.o piccontrol.c
ccache arm-oe-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mthumb
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
-I/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include/lua5.1
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-c -o ts209.o ts209.c
ccache arm-oe-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mthumb
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
-I/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include/lua5.1
-isystem/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/include
-c -o evdev.o evdev.c
ccache arm-oe-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s
-mthumb-interwork -mthumb -o piccontrol piccontrol.o ts209.o evdev.o
-L/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/lib
-Wl,-rpath-link,/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/lib
-Wl,-O1 -Wl,--hash-style=gnu
/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/lib/liblua5.1.a
-lpthread -lm -ldl
arm-oe-linux-gnueabi-gcc:
/media/work-disk/workdir/arm-926ejs-test/staging/armv5te-oe-linux-gnueabi/lib/liblua5.1.a:
No such file or directory
for more information, please see the following url:
http://tinderbox.openembedded.net/packages/451539/
Is there anyone who can give me some information?
Thanks a lot!
--
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com
next reply other threads:[~2010-01-31 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 3:01 Guo Hongruan [this message]
2010-01-31 5:22 ` building piccontrol - 0.4 failed due to lack of liblua5.1.a Khem Raj
2010-01-31 5:43 ` Guo Hongruan
2010-01-31 5:44 ` Guo Hongruan
2010-01-31 5:56 ` Guo Hongruan
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.u7dmmldamn1qzu@camelguo \
--to=camelguo@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tim.ellis@foonas.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.