From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: alsa-utils failure
Date: Mon, 16 Aug 2010 19:20:23 -0700 [thread overview]
Message-ID: <4C69F1E7.50000@balister.org> (raw)
At least one other person is seeing this. Mine is on a clean build on a
new F13 machine. Any thoughts?
Philip
gnueabi/alsa-utils-1.0.20-r2/alsa-utils-1.0.20/po'
| make[1]: Nothing to be done for `all'.
| make[1]: Leaving directory
`/home/balister/oe/tmp/work/armv7a-angstrom-linux-gnueabi/alsa-utils-1.0.20-r2/alsa-utils-1.0.20/po'
| Making all in alsamixer
| make[1]: Entering directory
`/home/balister/oe/tmp/work/armv7a-angstrom-linux-gnueabi/alsa-utils-1.0.20-r2/alsa-utils-1.0.20/alsamixer'
| arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-DCURSESINC="<ncurses.h>"
-isystem/home/balister/oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include
-fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
-ggdb3
-L/home/balister/oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
-Wl,-rpath-link,/home/balister/oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
-Wl,-O1 -Wl,--hash-style=gnu -o alsamixer alsamixer.o -lncurses -ltinfo
-lasound -lm -ldl -lpthread
|
/home/balister/oe/tmp/sysroots/x86_64-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/bin/ld:
cannot find -ltinfo
| collect2: ld returned 1 exit status
| make[1]: *** [alsamixer] Error 1
| make[1]: Leaving directory
`/home/balister/oe/tmp/work/armv7a-angstrom-linux-gnueabi/alsa-utils-1.0.20-r2/alsa-utils-1.0.20/alsamixer'
| make: *** [all-recursive] Error 1
| FATAL: oe_runmake failed
| ERROR: Function do_compile failed
NOTE: package alsa-utils-1.0.20-r2: task do_compile: Failed
next reply other threads:[~2010-08-17 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 2:20 Philip Balister [this message]
2010-08-17 5:03 ` alsa-utils failure Martin Jansa
2010-08-17 5:21 ` Khem Raj
2010-08-17 6:11 ` Martin Jansa
2010-08-17 5:09 ` Khem Raj
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=4C69F1E7.50000@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox